On Wed, 08 Sep 2010 18:31:30 -0400, Robert Buck wrote: > > We just switched over to git and also use gitolite. > > To create a new branch and push it so a team of developers can > collaborate on that branch I performed the following commands: > > Listed available tags: > git fetch --tags > > Listed available branches, which for me only showed one, master: > git branch > > Created the branch off the tag: > git branch fullers tagduvel > > Checked out the branch to verify the contents: > git checkout fullers > ... > > Push the branch to the remote repository: > git push origin fullers > > Now, when I clone the repository and list the branches I only see > 'master'. If I list the branches with the -a option I see something I > did not anticipate: > git branch -a > * master > remotes/origin/HEAD -> origin/master > remotes/origin/duvel > remotes/origin/fullers > remotes/origin/master > > What I had expected was a fullers branch. > > So apparently I did something very wrong here. What did I do wrong? > > Thanks, > > Bob You didn't do anything wrong at all. That's exactly what I'd expect to see at the end. Git doesn't automatically create local branches (the ones without remotes/.../ in front) for any branches other than the one pointed to by remotes/origin/HEAD. The other developers will still have your fullers branch available to them, but if they want to do any work on it, they'll need to do something like "git checkout -b fullers origin/fullers" to create a local branch, which they can modify. -- Jacob Helwig
Attachment:
signature.asc
Description: Digital signature