git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] helping smart-http/stateless-rpc fetch race
Date: Sun, 07 Aug 2011 22:03:43 -0700	[thread overview]
Message-ID: <7vbow01ols.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAJo=hJvdMCyU-5wzy0p1r+QJxXU=DJTE+Mu5G6pk9iAwAD51mA@mail.gmail.com> (Shawn Pearce's message of "Sat, 6 Aug 2011 14:05:31 -0700")

Shawn Pearce <spearce@spearce.org> writes:

> Why a new --allow-non-tip flag? Why not always do this with the
> existing --stateless-rpc flag?

It certainly would be much easier from implementation point of view, but I
did it that way for two and half reasons:

 (1) It might make sense to give admins who run upload-pack not behind
     smart-http an option to allow fetching from a non-tip; and

 (2) It also might make sense to let admins who do run upload-pack behind
     smart-http force re-fetching when the race is encountered.

and the remaining half-reason was that I was too lazy to think things
through to refute the above two "might make sense" and convince myself
that they should instead be "is not necessary".

  reply	other threads:[~2011-08-08  5:03 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 [this message]
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

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=7vbow01ols.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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).