From: "Remo Senekowitsch" <remo@buenzli•dev>
To: "Drew DeVault" <drew@ddevault•org>, <git@vger•kernel.org>
Cc: "Martin von Zweigbergk" <martinvonz@google•com>,
"Patrick Steinhardt" <ps@pks•im>,
"Andy Koppe" <andy.koppe@gmail•com>
Subject: Re: [PATCH v2 1/2] pretty: add X-Change-ID to mail formats
Date: Tue, 19 Aug 2025 19:45:34 +0200 [thread overview]
Message-ID: <DC6LB8FINRXH.1TMZPB1XKPQWQ@buenzli.dev> (raw)
In-Reply-To: <20250703113505.11889-1-drew@ddevault.org>
On Thu Jul 3, 2025 at 1:29 PM CEST, Drew DeVault wrote:
> Introduce the X-Change-ID header to emails prepared by git (i.e. via
> format-patch, send-email). This allows tools which work with those
> emails (e.g. patchwork, sourcehut) to meaningfully integrate with tools
> that assign change IDs to commits.
>
> With some follow-up work, this is also the first step towards ensuring
> that those change IDs are preserved through from git-send-email to
> git-am as a change moves through its review lifecycle.
Hi Drew,
Do you intend to keep working on this by any chance? I'm writing a code
review tool that relies on Jujutsu's change-id header for its "killer
feature". It will also support different code review platforms as
backends, including GitHub, mailing lists and more. As long as mailing
lists do not preserve the change-id header though, users of them will
fundamentally have a degraded experience.
That is to say, your efforts here are much appreciated. :-)
Best,
Remo
next prev parent reply other threads:[~2025-08-19 17:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 11:29 [PATCH v2 1/2] pretty: add X-Change-ID to mail formats Drew DeVault
2025-07-03 11:29 ` [PATCH v2 2/2] am: import X-Change-ID from email headers Drew DeVault
2025-07-06 3:37 ` [PATCH v2 1/2] pretty: add X-Change-ID to mail formats Jeff King
2025-07-06 10:46 ` Drew DeVault
2025-07-06 6:20 ` Aditya Garg
2025-07-06 10:41 ` Drew DeVault
2025-07-07 1:30 ` Junio C Hamano
2025-07-07 5:53 ` Junio C Hamano
2025-07-07 6:57 ` Martin von Zweigbergk
2025-07-07 6:59 ` Martin von Zweigbergk
2025-07-07 12:40 ` Junio C Hamano
2025-07-07 7:12 ` Drew DeVault
2025-07-07 7:09 ` Drew DeVault
2025-08-19 17:45 ` Remo Senekowitsch [this message]
2025-08-20 7:29 ` Drew DeVault
2025-08-21 0:50 ` Junio C Hamano
2025-08-21 8:52 ` Drew DeVault
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=DC6LB8FINRXH.1TMZPB1XKPQWQ@buenzli.dev \
--to=remo@buenzli$(echo .)dev \
--cc=andy.koppe@gmail$(echo .)com \
--cc=drew@ddevault$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=martinvonz@google$(echo .)com \
--cc=ps@pks$(echo .)im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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