From: Dave Borowitz <dborowitz@google.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: git <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Michael Haggerty <mhagger@alum.mit.edu>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: reftable [v4]: new ref storage format
Date: Mon, 31 Jul 2017 13:41:42 -0400 [thread overview]
Message-ID: <CAD0k6qTLSghs2Z6iv+kVQe091b+6=zqcR1k7_2eGks01rWUAsQ@mail.gmail.com> (raw)
In-Reply-To: <CAJo=hJv7scc1L0_MdRkFeLAJGjYm2UkTFNOgj2e4+9Zj7KSiiQ@mail.gmail.com>
On Sun, Jul 30, 2017 at 11:51 PM, Shawn Pearce <spearce@spearce.org> wrote:
> - Near constant time verification a SHA-1 is referred to by at least
> one reference (for allow-tip-sha1-in-want).
I think I understated the importance of this when I originally brought
up allow-tip-sha1-in-want. This is an important optimization for *any*
HTTP server, even without allow-tip-sha1-in-want, in order to validate
the SHA-1s sent in the upload-pack request, which doesn't share memory
state with the /info/refs request processing.
next prev parent reply other threads:[~2017-07-31 17:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 3:51 reftable [v4]: new ref storage format Shawn Pearce
2017-07-31 17:41 ` Dave Borowitz [this message]
2017-07-31 19:01 ` Stefan Beller
2017-07-31 23:05 ` Shawn Pearce
2017-07-31 19:42 ` Junio C Hamano
2017-07-31 23:43 ` Shawn Pearce
2017-08-01 16:08 ` Shawn Pearce
2017-08-01 6:41 ` Michael Haggerty
2017-08-01 20:23 ` Shawn Pearce
2017-08-02 0:49 ` Michael Haggerty
2017-08-01 23:27 ` Shawn Pearce
2017-08-01 23:54 ` Shawn Pearce
2017-08-02 1:51 ` Michael Haggerty
2017-08-02 2:38 ` Shawn Pearce
2017-08-02 9:28 ` Jeff King
2017-08-02 15:17 ` Shawn Pearce
2017-08-02 16:51 ` Junio C Hamano
2017-08-02 17:28 ` Jeff King
2017-08-02 12:20 ` Dave Borowitz
2017-08-02 17:18 ` Jeff King
2017-08-03 18:38 ` Michael Haggerty
2017-08-03 22:26 ` Shawn Pearce
2017-08-03 22:48 ` Michael Haggerty
2017-08-04 2:50 ` Shawn Pearce
2017-08-05 21:00 ` Shawn Pearce
2017-08-01 13:54 ` Dave Borowitz
2017-08-01 15:27 ` Shawn Pearce
2017-08-02 19:50 ` Junio C Hamano
2017-08-02 20:28 ` Jeff King
2017-08-03 22:17 ` Shawn Pearce
2017-08-03 1:50 ` Junio C Hamano
2017-08-03 2:21 ` Shawn Pearce
2017-08-03 2:36 ` Junio C Hamano
2017-08-02 19:54 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD0k6qTLSghs2Z6iv+kVQe091b+6=zqcR1k7_2eGks01rWUAsQ@mail.gmail.com' \
--to=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).