From: Jeff King <peff@peff.net>
To: martin f krafft <madduck@madduck.net>
Cc: git discussion list <git@vger.kernel.org>,
Petr Baudis <pasky@ucw.cz>, Clemens Buchacher <drizzd@aon.at>
Subject: Re: per-ref data storage (was: Storing additional information in commit headers)
Date: Wed, 3 Aug 2011 21:41:14 -0600 [thread overview]
Message-ID: <20110804034114.GB4534@sigill.intra.peff.net> (raw)
In-Reply-To: <20110802192727.GB20239@fishbowl.rw.madduck.net>
On Tue, Aug 02, 2011 at 09:27:28PM +0200, martin f krafft wrote:
> [sorry, my previous message was a total reply FAIL]
>
> also sprach martin f krafft <madduck@madduck.net> [2011.08.02.2106 +0200]:
> > It just seems to me that per-ref storage is a lot further away than
> > per-commit storage, and I'd really like to move forward with TopGit…
>
> refs/heads/master is a file, containing its payload in the first
> line by format definition, right?
>
> I mean: the storage is right there, isn't it?
Yes, and I think git will even ignore other stuff in the file. But I
don't think you can count on git not obliterating the other stuff when
it updates the ref. Nor would it be passed over a clone or fetch.
> Of course this opens a whole new can of worms: merging per-ref data.
Yes. That's the tricky part. And that's something you'll have to deal
with no matter how you store it, I expect.
-Peff
next prev parent reply other threads:[~2011-08-04 3:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 18:20 Storing additional information in commit headers martin f krafft
2011-08-01 18:27 ` Sverre Rabbelier
2011-08-01 18:34 ` martin f krafft
2011-08-01 20:01 ` Clemens Buchacher
2011-08-01 20:55 ` martin f krafft
2011-08-01 18:28 ` martin f krafft
2011-08-01 19:33 ` Martin Langhoff
2011-08-01 20:51 ` martin f krafft
2011-08-01 20:13 ` Jeff King
2011-08-01 21:11 ` martin f krafft
2011-08-02 3:50 ` Jeff King
2011-08-02 8:28 ` martin f krafft
2011-08-02 15:03 ` working prototype of orphan parent commits as datastores (was: Storing additional information in commit headers) martin f krafft
2011-08-02 18:57 ` Jeff King
2011-08-02 19:09 ` martin f krafft
2011-08-02 19:26 ` martin f krafft
2011-08-02 18:51 ` Storing additional information in commit headers Jeff King
2011-08-02 19:06 ` martin f krafft
2011-08-02 19:27 ` per-ref data storage (was: Storing additional information in commit headers) martin f krafft
2011-08-02 21:12 ` per-ref data storage martin f krafft
2011-08-04 3:41 ` Jeff King [this message]
2011-08-04 3:39 ` Storing additional information in commit headers Jeff King
2011-08-02 13:53 ` Michael Haggerty
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=20110804034114.GB4534@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=pasky@ucw.cz \
/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).