From: Junio C Hamano <gitster@pobox.com>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Does anyone use git-notes?
Date: Wed, 25 Aug 2010 15:43:16 -0700 [thread overview]
Message-ID: <7vd3t6pb3v.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTin=VXp2BU0vhTLUy6MpJ7spXRs1dZC1wygoN6T-@mail.gmail.com> (Scott Chacon's message of "Wed\, 25 Aug 2010 11\:15\:31 -0700")
Scott Chacon <schacon@gmail.com> writes:
> I would like to write a post on how to use them, but I'm a bit
> confused as to how people actually use them on a day to day basis. I
> appears to me in trying to work out a flow for them that the lack of
> an ability to merge them makes them very difficult to use for anything
> practical. Can someone share with me how they use them and what the
> cycle is?
I have a custom post-applypatch hook (see my "todo" branch) enabled and
then use the amlook script (again, see my "todo" branch) to inspect the
notes the hook left.
After applying a received patch e-mail, the result is annotated with
enough information to identify which message it came from by the hook (I
probably should add more information to the notes, but never got around to
it). When I am scouring the mailing list backlog to see if I have missed
something interesting (sometimes I find interest in a topic that I thought
totally uninteresting earlier), the amlook script is used to see if the
patch has already been applied, and if so to which branch.
Looking through millions of notes this way won't scale (iow, amlook is a
bad example of using this feature, as the notes tree is used as a database
index in the wrong direction), by the way, so you may probably not want to
use it as a good example.
next prev parent reply other threads:[~2010-08-25 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 18:15 Does anyone use git-notes? Scott Chacon
2010-08-25 18:40 ` Joshua Jensen
2010-08-25 18:52 ` Thomas Rast
2010-08-25 22:42 ` Junio C Hamano
2010-08-25 22:43 ` Junio C Hamano [this message]
2010-08-26 7:56 ` Tor Arntsen
2010-08-26 8:09 ` Michael J Gruber
2010-08-26 13:09 ` Will Palmer
2010-08-26 8:26 ` Jon Seymour
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=7vd3t6pb3v.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=schacon@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.