On Mon, 10 Jan 2011, Curtis Olson wrote: > remote: Total 1 (delta 0), reused 0 (delta 0) > Unpacking objects: 100% (1/1), done. >> From gitorious.org:fg/simgear > * [new branch] releases/2.2.0 -> origin/releases/2.2.0 > * [new tag] 2.2.0-rc1 -> 2.2.0-rc1 > Already up-to-date. > > > Ok, cool I think, it looks like the 2.2.0 release branch has been created. > > But my question is how can I switch to this new branch? When I list my > branches I see: > > simgear$ git branch > maint > * next > > > The new branch is not listed. Does this branch only exist on the server? > What do I have to do to see the branch locally? Do I have to manually copy > any remote branch that I want to work with locally? What's the git thought > process and reasoning here? How would a person typically know that a new > remote branch got created and be able to access it? Why doesn't the new > branch automatically show up in my list of branches?
Hi, It exists locally as a remote branch. Create a local branch based on it with git branch -t -l my-2.2.0 origin/releases/2.2.0 Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel