Re: Creating own hierarchies under $GITDIR/refs ?

From: John Keeping <john@keeping.me.uk>
Date: Feb 2, 2014, 11:31 UTC
Message-ID: <20140202113141.GB29976@serenity.lan>
In-Reply-To: <8761ox2240.fsf@fencepost.gnu.org>

On Sun, Feb 02, 2014 at 12:19:43PM +0100, David Kastrup wrote:

Show 12 quoted lines

> Duy Nguyen <pclouds@gmail.com> writes:
> 
> > The file is for past commits only.
> 
> > New commits can contain these info in their messages.
> 
> If it's not forgotten.  Experience shows that things like issue numbers
> have a tendency to be omitted, and then they stay missing.
> 
> At any rate, this is exactly the kind of stuff that tags are useful for,
> except that using them for all that would render the "tag space"
> overcrowded.

Actually, I would say this is exactly the sort of thing notes are for.

git.git uses them to map commits back to mailing list discussions:

    git fetch git://github.com/gitster/git +refs/notes/amlog:refs/notes/amlog &&
    git log --notes=amlog

See also notes.displayRef in git-config(1).

Notes aren't fetch by default, but it's not hard for those interested to add a remote.*.fetch line to their config.