Re: Useful tracking branches and auto merging

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Oct 5, 2010, 17:49 UTC
Message-ID: <AANLkTinXJ5E_U=5uP_zvWLQBssQsYC74JyVv1N3-eMXK@mail.gmail.com>
In-Reply-To: <7vk4lw7g2m.fsf@alter.siamese.dyndns.org>

On Tue, Oct 5, 2010 at 7:35 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 9 quoted lines

> Jonathan Nieder <jrnieder@gmail.com> 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