Re: Storing additional information in commit headers
- From
Clemens Buchacher <drizzd@aon.at>
- Date
- Aug 1, 2011, 20:01 UTC
- Message-ID
- <20110801200149.GA20861@toss>
- 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