Re: [PATCH v2 1/2] pretty: add X-Change-ID to mail formats
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 21, 2025, 00:50 UTC
- Message-ID
- <xmqq4iu17b1y.fsf@gitster.g>
- In-Reply-To
- <DC72UF1IMIUF.2F7CNYOHYDGVJ@ddevault.org>
"Drew DeVault" <drew@ddevault.org> writes:
> I haven't gotten much actionable feedback on this patch yet, > so there's not much to do here but wait for more reviewers.
For a topic that is older than 6 weeks, I am afraid that is a losing strategy. People who might have cared about the topic said all they wanted to say, new people are less likely to discover the topic than it was fresh, and unless you make an action (e.g., posting the "next patch version" you mentioned in [*1*]), it is highly unlikely for anything to happen while you are passive. Even a small update that addresses all the little feedback would serve as a "ping" to reignite interests.
You seem to have liked the approach to generalize and encode all the commit object headers (except for of course the object name and author and committer ident, which already have place to be in the format-patch output) on an e-mail header in [*2*]. That should be sufficient for a small update that tries to reignite interests.
[References]
*1* https://lore.kernel.org/git/DB4WU136IYR2.3ELSGQUDD6QI8@ddevault.org/ *2* https://lore.kernel.org/git/DB5MUUDPF6C0.3OR02N6JQB8H8@ddevault.org/