From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Michael S. Tsirkin" <mst@mellanox.co.il>, git@vger.kernel.org
Subject: Re: RFC: git pull <remote> making an octopus?
Date: Tue, 15 Aug 2006 09:40:06 +0200 [thread overview]
Message-ID: <81b0412b0608150040m422e695fl68650dad6b692533@mail.gmail.com> (raw)
In-Reply-To: <7vk65bdm9f.fsf@assigned-by-dhcp.cox.net>
On 8/14/06, Junio C Hamano <junkio@cox.net> wrote:
> - when dealing with the refspecs from the shorthand
> (.git/remotes), the one on the first "Pull: " line is for
> merge and everything else is not.
What happens if you have _many_ refspecs in a "Pull:"-line?
next prev parent reply other threads:[~2006-08-15 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 6:43 RFC: git pull <remote> making an octopus? Michael S. Tsirkin
2006-08-14 7:00 ` Junio C Hamano
2006-08-14 7:53 ` Michael S. Tsirkin
2006-08-14 17:55 ` Michael S. Tsirkin
2006-08-14 21:45 ` Junio C Hamano
2006-08-15 7:40 ` Alex Riesen [this message]
2006-08-15 7:45 ` Junio C Hamano
2006-08-17 9:08 ` Junio C Hamano
2006-08-17 9:18 ` Alex Riesen
2006-08-17 9:46 ` Michael S. Tsirkin
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=81b0412b0608150040m422e695fl68650dad6b692533@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mst@mellanox.co.il \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox