From: John Keeping <john@keeping.me.uk>
To: David Kastrup <dak@gnu.org>
Cc: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Creating own hierarchies under $GITDIR/refs ?
Date: Sun, 2 Feb 2014 11:31:41 +0000 [thread overview]
Message-ID: <20140202113141.GB29976@serenity.lan> (raw)
In-Reply-To: <8761ox2240.fsf@fencepost.gnu.org>
On Sun, Feb 02, 2014 at 12:19:43PM +0100, David Kastrup wrote:
> 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.
next prev parent reply other threads:[~2014-02-02 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 10:37 Creating own hierarchies under $GITDIR/refs ? David Kastrup
2014-02-02 11:00 ` Duy Nguyen
2014-02-02 11:19 ` David Kastrup
2014-02-02 11:31 ` John Keeping [this message]
2014-02-02 11:42 ` David Kastrup
2014-02-02 12:24 ` John Keeping
2014-02-02 23:44 ` Jed Brown
2014-02-02 12:00 ` Duy Nguyen
2014-02-02 12:09 ` David Kastrup
2014-02-02 11:04 ` Andreas Schwab
2014-02-02 23:26 ` Jeff King
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=20140202113141.GB29976@serenity.lan \
--to=john@keeping.me.uk \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=pclouds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.