The release branches are ready and the next/master branches are open
again for cool, great and fancy new features.
James: Please introduce the new release branches to Jenkins
ThorstenB: Please do so for the OBS
Curt: Please create a release candidate from the release/2.6.0 build
once James has
On Tue, 17 Jan 2012, Torsten Dreyer wrote:
The release branches are ready and the next/master branches are open
again for cool, great and fancy new features.
James: Please introduce the new release branches to Jenkins
ThorstenB: Please do so for the OBS
Curt: Please create a release
Hi Torsten,
Can you post a quick git reminder for how to checkout the release/2.6.0
branch. I'm sure I'm not the only one who forgets something he hasn't
thought about in 6 months. :-)
Thanks,
Curt.
On Tue, Jan 17, 2012 at 2:01 AM, Torsten Dreyer tors...@t3r.de wrote:
The release branches
On Tue, 17 Jan 2012, Curtis Olson wrote:
Hi Torsten,
Can you post a quick git reminder for how to checkout the release/2.6.0
branch. I'm sure I'm not the only one who forgets something he hasn't
thought about in 6 months. :-)
You can do this:
git fetch
git branch -t -l release-2.6.0
On Tue, 17 Jan 2012, Anders Gidenstam wrote:
You can do this:
git fetch
git branch -t -l release-2.6.0 origin/release/2.6.0
git checkout release-2.6.0
However, if you have a update to push that would then need to be
git push origin release-2.6.0:release/2.6.0
to go to the right remote
Anders Gidenstam wrote:
git branch -t -l release-2.6.0 origin/release/2.6.0
where -t refers to origin/release/2.6.0, therefore:
release-2.6.0 -t origin/release/2.6.0
might be easier to memorize.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about
On Tue, Jan 17, 2012 at 2:01 AM, Torsten Dreyer tors...@t3r.de wrote:
The release branches are ready and the next/master branches are open
again for cool, great and fancy new features.
James: Please introduce the new release branches to Jenkins
Hi James,
Would you mind posting when the
7 matches
Mail list logo