From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: [RFC/RFH] Fun things with git-notes, or: patch tracking backwards
Date: Tue, 10 Feb 2009 14:59:27 -0800 [thread overview]
Message-ID: <7v7i3xlwz4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200902102342.29962.trast@student.ethz.ch> (Thomas Rast's message of "Tue, 10 Feb 2009 23:42:27 +0100")
Thomas Rast <trast@student.ethz.ch> writes:
> I have imported all commits, and mails since roughly July 2008
> (starting with Gmane 89000). In this timeframe there were 1802
> non-merge commits, and the mailnotes tree now holds 1122 annotations.
How do you match the mails to commits?
I am curious what the right balance for the matching algorithm should be,
between being forgiving about amending of commit log message and the patch
text to fix minor typos and obvious bugs, and being strict not to cause
false matches to a message that contains the second iteration of the
patch, when what was committed was the first iteration.
next prev parent reply other threads:[~2009-02-10 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 14:08 [RFC/RFH] Fun things with git-notes, or: patch tracking backwards Thomas Rast
2009-02-09 16:19 ` SZEDER Gábor
2009-02-09 16:29 ` Thomas Rast
2009-02-09 17:49 ` tool and worktree Giuseppe Bilotta
2009-02-10 22:42 ` [RFC/RFH] Fun things with git-notes, or: patch tracking backwards Thomas Rast
2009-02-10 22:52 ` Junio C Hamano
2009-02-10 22:59 ` Junio C Hamano [this message]
2009-02-10 23:12 ` Thomas Rast
2009-02-10 23:30 ` Junio C Hamano
2009-02-11 22:52 ` Thomas Rast
2009-02-11 22:58 ` Thomas Rast
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=7v7i3xlwz4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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).