From: Junio C Hamano <gitster@pobox.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
Sverre Rabbelier <srabbelier@gmail.com>,
git@vger.kernel.org
Subject: Re: [RFC] helping smart-http/stateless-rpc fetch race
Date: Mon, 08 Aug 2011 16:42:27 -0700 [thread overview]
Message-ID: <7vei0vtqqk.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAJo=hJu=nuy8Ws8PP16F=ay-Wp9vAdW_U113WLVCFs4hPQOeQA@mail.gmail.com> (Shawn Pearce's message of "Mon, 8 Aug 2011 16:33:13 -0700")
Shawn Pearce <spearce@spearce.org> writes:
> On Mon, Aug 8, 2011 at 16:26, Junio C Hamano <gitster@pobox.com> wrote:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> A separate option would allow admins to let their clients ask to fetch
>>> 4bc5fbf (that is v0.99~2) even if that commit is not at the tip of any ref
>>> if they choose to. That is what (1) is about, and people who do not want
>>> a separate option needs to argue that it is an unnecessary "feature".
>>
>> By the way, I personally do not think it is necessary, but as long timers
>> on the list may recall, this has come up on the list for a few times.
>
> My feeling is clients aren't likely to do this, or grow this feature
> anytime soon, so why add a backend option for it now? Lets add the
> feature when the feature is necessary... and right now just fix the
> race in smart HTTP.
Yes, that is what is queued in today's 'pu'.
prev parent reply other threads:[~2011-08-08 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 20:54 [RFC] helping smart-http/stateless-rpc fetch race Junio C Hamano
2011-08-06 21:05 ` Shawn Pearce
2011-08-08 5:03 ` Junio C Hamano
2011-08-08 17:13 ` Junio C Hamano
2011-08-08 21:05 ` Sverre Rabbelier
2011-08-08 23:08 ` Ilari Liusvaara
2011-08-08 23:24 ` Junio C Hamano
2011-08-08 23:26 ` Junio C Hamano
2011-08-08 23:33 ` Shawn Pearce
2011-08-08 23:42 ` Junio C Hamano [this message]
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=7vei0vtqqk.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=spearce@spearce.org \
--cc=srabbelier@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.