From: Eric Wong <e@80x24.org>
To: Emily Shaffer <nasamuffin@google.com>
Cc: git@vger.kernel.org
Subject: Re: Linking topic merges to mailing list threads
Date: Wed, 2 Oct 2024 22:50:57 +0000 [thread overview]
Message-ID: <20241002225057.M796260@dcvr> (raw)
In-Reply-To: <CAJoAoZ=4ARuH3aHGe5yC_Xcnou_c396q_ZienYPY7YnEzZcyEg@mail.gmail.com>
Emily Shaffer <nasamuffin@google.com> wrote:
> Hi all,
>
> We've been wanting to gather metrics on Git's code review process -
> how long it takes from first contact on list to merge, how many
> iterations are needed, time between iterations, etc. One missing link
> is the actual merge time in `next` and `master` - a human can infer
> the link between the patch and the mailing list thread, but it's more
> challenging for a script to do it.
Searching by commit titles as a phrase against email subject (`s:')
can probably make it easy w/o having to look up amlog or explicitly
keep track of human-unmemorizable metadata such as Message-IDs.
Example:
https://80x24.org/lore/pub/scm/git/git.git/365529e1ea19b44a7a253b780f3ae3a1cb2f081f/s/#merged
...In the "find merged patch emails" textarea. Yeah it's part of a
100% JS-free alternative to cgit, gitweb, etc...
(https://public-inbox.org/meta/20241002223902.4139389-4-e@80x24.org/
implements the query generation)
next prev parent reply other threads:[~2024-10-02 22:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 16:21 Linking topic merges to mailing list threads Emily Shaffer
2024-09-30 16:57 ` Konstantin Ryabitsev
2024-09-30 19:30 ` Junio C Hamano
2024-09-30 20:45 ` [PATCH] Documentation: mention the amlog in howto/maintain-git.txt Taylor Blau
2024-09-30 21:06 ` Kristoffer Haugsbakk
2024-10-02 15:04 ` Taylor Blau
2024-09-30 21:54 ` Junio C Hamano
2024-10-02 15:05 ` Taylor Blau
2024-10-02 15:03 ` [PATCH v2] " Taylor Blau
2024-10-02 19:47 ` Junio C Hamano
2024-10-03 1:09 ` Taylor Blau
2024-10-03 1:09 ` [PATCH v3] " Taylor Blau
2024-10-03 17:23 ` Junio C Hamano
2024-10-03 18:32 ` Ramsay Jones
2024-10-03 18:44 ` Taylor Blau
2024-09-30 20:41 ` Linking topic merges to mailing list threads Kristoffer Haugsbakk
2024-10-02 22:50 ` Eric Wong [this message]
2024-10-02 23:34 ` 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=20241002225057.M796260@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=nasamuffin@google.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.