Re: how do I create a branch and push it so several developers can share work?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Jacob. I thought I had done it right, but when I cloned and did
not get what I expected at first, I was a bit concerned. Thanks.

Related question, is there a way to have fullers show up automatically
as a local branch for developers simply through a `git clone`?



On Wed, Sep 8, 2010 at 6:40 PM, Jacob Helwig <jacob.helwig@xxxxxxxxx> wrote:
> 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
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQGcBAEBAgAGBQJMiBDiAAoJEHJabXWGiqEBu1cL+gNCu5BiRFytPSi7IsjPNk81
> dPO6AX69K1hq22eShO0Li62NPDhM4B8H5aXAlfdtjVLz/VdRrAiuBaW2zX0eUaQ6
> i7k3vl+QeyDt02UphG9mM8dEYivrh7UUozQ3OVTYitkN5+3kmfg7tw+7pF7+Z6Et
> LZ7bRUb3pzEaD8sKSKNbqjSpj9bqo2aCdgZFd+fE8yzNDmpE6wQby9vks15IOtPd
> Skh+SjhmD9yNL6LC3+8989muxXomi2gZvXIcCyBy/ECexeLSTOQGH6JX086TIqus
> rVKn7UNNncNzB2Q/lY8VM89A7zTyEdFhIbh8xkbEEGPGkGTU3t/TOwANGU0Q3rRO
> ymNJYLhg9cg+JWnO04f5gTPI66df4J16ctqIEWqBiqK6gm+8/VlLyz2H4yIvxRfW
> zocPp3ae/JsKIYKAqBPwFaeNgW4mHMmLlnv6Gc96ZscFE66dj5HgwuY80B6pNSqR
> U3H3VJGWNJsAceByhArsaytrzLURbxqpE4a79IuVIg==
> =fj56
> -----END PGP SIGNATURE-----
>
>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]