Re: Useful tracking branches and auto merging

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

 



On Tue, Oct 5, 2010 at 7:35 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Jonathan Nieder <jrnieder@xxxxxxxxx> writes:
>
>> Maybe 'git pull --all' could be taught to eventually do this? ÂThat
>> would be incompatible with its current behavior of fetching everything
>> and merging some random branch, but I don't think anyone is relying
>> on that.
>
> I vaguely recall that we had discussions to disable "git pull --all",
> which most likely is a mistake?

I believe this use-case is valid:

 * The user wants *all* his remote tracking branches to point to the
latest branch head in all the repos in the case the can be
fast-forwarded, and in the case they can't, print an error and
continue with the rest.

Right now I would have to do 'git fetch --all' go to every remote
tracking branch, and do 'git merge @{upstream}'.

Do you have a better idea how to achieve that instead of 'git pull --all'?

-- 
Felipe Contreras
--
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]