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

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

 



"Sverre Hvammen Johansen" <hvammen@xxxxxxxxx> writes:

> 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.

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

  Powered by Linux