From: Jeff King <firstname.lastname@example.org> To: Shawn Pearce <email@example.com> Cc: git <firstname.lastname@example.org>, David Turner <email@example.com>, Michael Haggerty <firstname.lastname@example.org> Subject: Re: RefTree: Alternate ref backend Date: Thu, 17 Dec 2015 17:10:45 -0500 [thread overview] Message-ID: <20151217221045.GA8150@sigill.intra.peff.net> (raw) In-Reply-To: <CAJo=hJvnAPNAdDcAAwAvU9C4RVeQdoS3Ev9WTguHx4fD0V_nOg@mail.gmail.com> On Thu, Dec 17, 2015 at 01:02:50PM -0800, Shawn Pearce wrote: > I started playing around with the idea of storing references directly > in Git. Exploiting the GITLINK tree entry, we can associate a name to > any SHA-1. Gitlink entries don't imply reachability, though. I guess that doesn't matter if your ref backend says "no, really, these are the ref tips, and they are reachable". But you could not push the whole thing up to another server and expect it to hold the whole graph. Which is not strictly necessary, but to me seems like the real advantage of using git objects versus some other system. Of course, the lack of reachability has advantages, too. You can drop commits pointed to by old reflogs without rewriting the ref history. Unfortunately you cannot expunge the reflogs at all. That's good if you like audit trails. Bad if you are worried that your reflogs will grow large. :) > By storing all references in a single tree, atomic transactions are > possible. Its a simple compare-and-swap of a single 40 byte SHA-1. > This of course leads to a bootstrapping problem, where do we store the > 40 byte SHA-1? For this example its just $GIT_DIR/refs/txn/committed > as a classical loose reference. Somehow putting it inside `refs/` seems weird to me, in an infinite recursion kind of way. I would have picked $GIT_DIR/REFSTREE or something. But that is a minor point. > Configuration: > > [core] > repositoryformatversion = 1 > [extensions] > refsBackendType = RefTree The semantics of extensions config keys are open-ended. The formatVersion=1 spec only says "if there is a key you don't know about, then you may not proceed". Now we're defining a refsBackendType extension. It probably makes sense to write up a few rules (e.g., is RefTree case-sensitive?). -Peff
next prev parent reply other threads:[~2015-12-17 22:11 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-17 21:02 Shawn Pearce 2015-12-17 21:57 ` Junio C Hamano 2015-12-17 22:15 ` Shawn Pearce 2015-12-17 22:10 ` Jeff King [this message] 2015-12-17 22:28 ` Shawn Pearce 2015-12-18 1:36 ` Mike Hommey 2015-12-22 15:41 ` Michael Haggerty 2015-12-22 16:11 ` Shawn Pearce 2015-12-22 17:04 ` Dave Borowitz 2015-12-22 17:17 ` Michael Haggerty 2015-12-22 18:50 ` Shawn Pearce 2015-12-22 19:09 ` Junio C Hamano 2015-12-22 19:11 ` Shawn Pearce 2015-12-22 19:34 ` Junio C Hamano 2015-12-23 4:59 ` Michael Haggerty 2015-12-24 1:33 ` Junio C Hamano [not found] ` <4689734.cEcQ2vR0aQ@mfick1-lnx> 2015-12-22 20:56 ` Martin Fick 2015-12-22 21:23 ` 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 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=20151217221045.GA8150@sigill.intra.peff.net \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: RefTree: Alternate ref backend' \ /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
Code repositories for project(s) associated with this 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).