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 branch. A slightly better alternativ would be to keep the local and remote branch name the same: git branch -t -l release/2.6.0 origin/release/2.6.0 git checkout release/2.6.0 Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://gitorious.org/anders-hangar http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
