Hey Tomas, others, I just updated the deltacloud.org website (both the git repository, and the live site). Note that I merged "next" onto master, pushed, and then put my changes directly on master. Might I suggest that we stop using the "next" branch for docs/, and instead always commit everything on master? I know that is a change from what we have done before, but it just doesn't make too much sense (to me) to have the split between master and next.
Thanks,
Hey Tomas, others, I just updated the deltacloud.org website (both the git repository, and the live site). Note that I merged "next" onto master, pushed, and then put my changes directly on master. Might I suggest that we stop using the "next" branch for docs/, and instead always commit everything on master?
I would love to see everything on master. +1
-- Ladislav
On 12/15/2010 10:28 AM, Ladislav Martincik wrote:
Hey Tomas, others, I just updated the deltacloud.org website (both the git repository, and the live site). Note that I merged "next" onto master, pushed, and then put my changes directly on master. Might I suggest that we stop using the "next" branch for docs/, and instead always commit everything on master?
I would love to see everything on master. +1
-- Ladislav
Yeah, I'm cool with the website being on a single (master) branch.
Thomas
On 12/15/10 - 11:24:34AM, Tomas Sedovic wrote:
On 12/15/2010 10:28 AM, Ladislav Martincik wrote:
Hey Tomas, others, I just updated the deltacloud.org website (both the git repository, and the live site). Note that I merged "next" onto master, pushed, and then put my changes directly on master. Might I suggest that we stop using the "next" branch for docs/, and instead always commit everything on master?
I would love to see everything on master. +1
-- Ladislav
Yeah, I'm cool with the website being on a single (master) branch.
OK, great. I've now deleted the next branch completely, so there is only the master branch in the docs/ repo.
deltacloud-devel@lists.fedorahosted.org