From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Koch <thomas@koch.ro>
Cc: git@vger.kernel.org
Subject: Re: git notes primer?
Date: Wed, 11 Aug 2010 00:10:36 -0500 [thread overview]
Message-ID: <20100811051036.GA639@burratino> (raw)
In-Reply-To: <201008101040.07172.thomas@koch.ro>
Hi Thomas,
Thomas Koch wrote:
> Before I continue with my current design, I wanted to have a look at git
> notes, whether it would provide better mechanisms then tracking my meta
> informations in a hidden background branch. (Much like pristine-tar does.)
“git notes” associates arbitrary data to specific objects (blobs, trees,
commits, annotated tags). If your metainformation is per-branch rather
than per-commit, then notes will probably not help you.
Feel free to be inspired by their design, though. :)
Regards,
Jonathan
next prev parent reply other threads:[~2010-08-11 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 8:40 git notes primer? Thomas Koch
2010-08-10 11:32 ` Michael J Gruber
2010-08-11 5:10 ` Jonathan Nieder [this message]
2010-08-11 9:52 ` Johan Herland
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=20100811051036.GA639@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=thomas@koch.ro \
/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).