From: Junio C Hamano <junkio@cox.net>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: git@vger.kernel.org
Subject: Re: Multiple pulls from the same branch in .git/remotes/origin
Date: Mon, 07 Aug 2006 12:53:29 -0700 [thread overview]
Message-ID: <7vu04o1fwm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060807193809.GA24013@mellanox.co.il> (Michael S. Tsirkin's message of "Mon, 7 Aug 2006 22:38:09 +0300")
"Michael S. Tsirkin" <mst@mellanox.co.il> writes:
>> It might not be too difficult to change it though. This part of
>> the code is relatively old and I do not remember the details
>> offhand, other than I remember that the first time I saw it I
>> had the same confused "Huh? we do not let a ref fetched twice?"
>> reaction ;-).
>
> At least, fix the error message?
That would touch the same vicinity of code so if I were to do
that myself I would rather see if the restriction can be
loosened properly first.
next prev parent reply other threads:[~2006-08-07 19:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 14:03 [PATCH] mailinfo: accept >From in message header Michael S. Tsirkin
2006-07-27 21:22 ` Junio C Hamano
2006-07-27 21:32 ` Michael S. Tsirkin
2006-08-07 12:51 ` Multiple pulls from the same branch in .git/remotes/origin Michael S. Tsirkin
2006-08-07 18:28 ` Junio C Hamano
2006-08-07 19:38 ` Michael S. Tsirkin
2006-08-07 19:53 ` Junio C Hamano [this message]
2006-08-07 21:05 ` Michael S. Tsirkin
2006-08-07 22:04 ` Junio C Hamano
2006-08-07 22:33 ` Michael S. Tsirkin
2006-08-07 22:19 ` [PATCH] Multiple refs from the same remote in one git fetch Michael S. Tsirkin
2006-08-07 23:05 ` Junio C Hamano
2006-08-12 22:39 ` Michael S. Tsirkin
2006-08-12 23:07 ` Junio C Hamano
2006-08-14 0:13 ` Michael S. Tsirkin
2006-08-14 0:20 ` Junio C Hamano
2006-08-14 5:13 ` Michael S. Tsirkin
2006-08-14 5:53 ` Junio C Hamano
2006-08-14 6:33 ` Michael S. Tsirkin
2006-08-14 7:34 ` Junio C Hamano
2006-08-14 7:42 ` Michael S. Tsirkin
2006-08-14 10:49 ` Jakub Narebski
2006-08-14 17:51 ` Michael S. Tsirkin
2006-08-14 18:33 ` Jakub Narebski
2006-08-14 19:17 ` Michael S. Tsirkin
2006-08-22 15:10 ` [PATCH repost] " Michael S. Tsirkin
2006-08-23 1:34 ` Junio C Hamano
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=7vu04o1fwm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).