From: Junio C Hamano <gitster@pobox•com>
To: "Drew DeVault" <drew@ddevault•org>
Cc: "Remo Senekowitsch" <remo@buenzli•dev>, <git@vger•kernel.org>,
"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: Wed, 20 Aug 2025 17:50:17 -0700 [thread overview]
Message-ID: <xmqq4iu17b1y.fsf@gitster.g> (raw)
In-Reply-To: <DC72UF1IMIUF.2F7CNYOHYDGVJ@ddevault.org> (Drew DeVault's message of "Wed, 20 Aug 2025 09:29:56 +0200")
"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/
next prev parent reply other threads:[~2025-08-21 0:50 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
2025-08-20 7:29 ` Drew DeVault
2025-08-21 0:50 ` Junio C Hamano [this message]
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=xmqq4iu17b1y.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--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 \
--cc=remo@buenzli$(echo .)dev \
/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