Re: [RFC/PATCH] Fast forward strategies only, common, fork and path

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 4, 2008, 07:31 UTC
Message-ID: <7vsl09kwjg.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <402c10cd0802032313la7d3a8cqa4ec34e100385fb4@mail.gmail.com>

"Sverre Hvammen Johansen" <hvammen@gmail.com> writes:

Show 6 quoted lines

> git-pull only accepts one repository.  With this patch it makes sense
> to accept more than one repository.  I would like to rewrite git-pull
> to accept more than one repository.  This might break compatibility
> with existing git-pull.  One solution could be to introduce a new
> command that does the same as git-pull and more.  What about naming
> such a command git-update and deprecate git-pull.

Just add contrib/multi-pull/ directory and put your shell script there, something like:

	#!/bin/sh
	append=
	for repo
        do
        	git fetch $append $repo
                append=--append
	done
	merge_name=$(git fmt-merge-msg <"$GIT_DIR/FETCH_HEAD")
        git merge -m "$merge_name" $(sed -e '/	not-for-merge	/d'
        		-e 's/	.*//' "$GIT_DIR/FETCH_HEAD")

If it turns out to be useful for many people, it may become part of the main Porcelain. It's too early to talk about touching git-pull at all.