From: Junio C Hamano <gitster@pobox.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: git <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Michael Haggerty <mhagger@alum.mit.edu>,
David Borowitz <dborowitz@google.com>
Subject: Re: reftable [v4]: new ref storage format
Date: Wed, 02 Aug 2017 18:50:37 -0700 [thread overview]
Message-ID: <xmqqd18dqv0y.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqh8xpsq9c.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Wed, 02 Aug 2017 12:50:39 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I like the general idea, what the file format can represent and how
> it does so, but I am a bit uneasy about how well this "stacked" part
> would work for desktop clients.
Two more random things before I forget.
* I understand that you would want to allow both a ref "ref/D" and
"ref/D/F" to appear in the same reftable file. A refname is an
uninterpreted sequence of bytes and refnames are sorted in the
table.
Would it benefit us if we define the sort order of bytes slightly
different from the ASCII order, so that a slash '/' sorts between
NUL '\000' and SOH '\001', which is the order we should have used
when storing the entries in the index?
* Even though readers can continue accessing, starting from the
$GIT_DIR/refs, without locking and get consistent views, any
transaction that groups one or more ref updates would need to
take a global lock on $GIT_DIR/refs file.
Would it become a problem in a busy repository?
next prev parent reply other threads:[~2017-08-03 1:50 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
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 [this message]
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=xmqqd18dqv0y.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=dborowitz@google.com \
--cc=git@vger.kernel.org \
--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).