From: Clemens Buchacher <drizzd@aon.at>
To: martin f krafft <madduck@madduck.net>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
git discussion list <git@vger.kernel.org>,
Petr Baudis <pasky@ucw.cz>
Subject: Re: Storing additional information in commit headers
Date: Mon, 1 Aug 2011 22:01:49 +0200 [thread overview]
Message-ID: <20110801200149.GA20861@toss> (raw)
In-Reply-To: <20110801183411.GA5182@fishbowl.rw.madduck.net>
On Mon, Aug 01, 2011 at 08:34:11PM +0200, martin f krafft wrote:
>
> Yes, I have considered git-notes. The issue I have with git-notes is
> that it requires every contributor to set up refspecs for fetch and
> push, or else the notes will not be exchanged/shared.
Notes are tracked using a 'branch' too. It's just a branch in the
refs/notes namespace, the notes ref. You could simply tag your
notes ref or point a ref from the refs/heads namespace to it each
time you create new notes.
> Also, git-notes are mutable (at least from the UI perspectiv) and
> I strive to encode information immutably.
Notes are also used by textconv, for example, to cache immutable
data. It's not likely a user will end up editing it by accident
unless you use the default notes ref.
Clemens
next prev parent reply other threads:[~2011-08-01 20:01 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 [this message]
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 ` per-ref data storage (was: Storing additional information in commit headers) Jeff King
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=20110801200149.GA20861@toss \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=pasky@ucw.cz \
--cc=srabbelier@gmail.com \
/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).