From: Junio C Hamano <gitster@pobox.com>
To: "Sverre Hvammen Johansen" <hvammen@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Fast forward strategies only, common, fork and path
Date: Sun, 03 Feb 2008 23:31:15 -0800 [thread overview]
Message-ID: <7vsl09kwjg.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <402c10cd0802032313la7d3a8cqa4ec34e100385fb4@mail.gmail.com> (Sverre Hvammen Johansen's message of "Sun, 3 Feb 2008 23:13:50 -0800")
"Sverre Hvammen Johansen" <hvammen@gmail.com> 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.
next prev parent reply other threads:[~2008-02-04 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 0:54 [RFC/PATCH] Fast forward strategies only, common, fork and path Sverre Hvammen Johansen
2008-02-04 4:49 ` Stefan (metze) Metzmacher
2008-02-04 6:51 ` Sverre Hvammen Johansen
2008-02-04 7:24 ` Junio C Hamano
2008-02-04 8:06 ` Sverre Hvammen Johansen
2008-02-04 8:22 ` Junio C Hamano
2008-02-05 7:32 ` Sverre Hvammen Johansen
2008-02-05 9:34 ` Jakub Narebski
2008-02-05 9:40 ` Junio C Hamano
2008-02-06 3:46 ` Sverre Hvammen Johansen
2008-02-04 7:13 ` Sverre Hvammen Johansen
2008-02-04 7:31 ` Junio C Hamano [this message]
2008-02-04 7:43 ` Sverre Hvammen Johansen
2008-02-04 7:19 ` Sverre Hvammen Johansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vsl09kwjg.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hvammen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.