git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Drew DeVault" <drew@ddevault.org>
To: "Jeff King" <peff@peff.net>
Cc: <git@vger.kernel.org>,
	"Martin von Zweigbergk" <martinvonz@google.com>,
	"Patrick Steinhardt" <ps@pks.im>,
	"Andy Koppe" <andy.koppe@gmail.com>,
	"Remo Senekowitsch" <remo@buenzli.dev>
Subject: Re: [PATCH v2 1/2] pretty: add X-Change-ID to mail formats
Date: Sun, 06 Jul 2025 12:46:01 +0200	[thread overview]
Message-ID: <DB4WU136IYR2.3ELSGQUDD6QI8@ddevault.org> (raw)
In-Reply-To: <20250706033710.GD3041790@coredump.intra.peff.net>


[-- Attachment #1.1.1: Type: text/plain, Size: 597 bytes --]

On Sun Jul 6, 2025 at 5:37 AM CEST, Jeff King wrote:
> I don't have any opinion on the feature itself, but the plumbing way to
> do it would perhaps be:
>
>   # make some vanilla commit...
>   git commit -m foo &&
>
>   # make a new variant with the change id
>   commit=$(
>     git cat-file commit HEAD |
>     perl -lpe 'print "change-id foo" unless length' |
>     git hash-object -w --stdin -t commit
>   ) &&
>
>   # replace the old one
>   git update-ref HEAD $commit

Thanks! I'll incorporate this into the tests in the next patch version
after some further discussion.

[-- Attachment #1.2: 42F3F1862E3CC4B8.asc --]
[-- Type: application/pgp-keys, Size: 644 bytes --]

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEZ7Y9kxYJKwYBBAHaRw8BAQdA/pPy6X+nNL5T2QaJKEM08xN/Kz7wFTAZoH5Y
riV9x1m0IERyZXcgRGVWYXVsdCA8ZHJld0BkZGV2YXVsdC5vcmc+iJMEExYKADsC
GwMFCwkIBwICIgIGFQoJCAsCBBYCAwECHgcCF4AWIQSftec33CWynY7sRpFC8/GG
LjzEuAUCZ7Y9wwAKCRBC8/GGLjzEuMEEAP9DH+1LgvTqZDLZ8babB5Cdp5y0ZW+Q
Tx78mh1L8jJd6gEAssmgsImcrZv4adP2UW5RU5BHCe9KUdx0DyV83QwlFAS4OARn
tj2TEgorBgEEAZdVAQUBAQdAGAH9dlaCONoXpmQgHoQgYI2tS+VM3mzU8I2PyVYQ
1GUDAQgHiHgEGBYKACACGwwWIQSftec33CWynY7sRpFC8/GGLjzEuAUCZ7Y91gAK
CRBC8/GGLjzEuHcnAP4yjOiM0yqkST6yXzDUWze7B9Im24F8HVx+wNqcDaDtcAD/
fKQhz0SCPiblO6lc7MFUvlaOz2v87UpUYRhzPdgQqwk=
=emrb
-----END PGP PUBLIC KEY BLOCK-----

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-07-06 10:46 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 [this message]
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
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=DB4WU136IYR2.3ELSGQUDD6QI8@ddevault.org \
    --to=drew@ddevault.org \
    --cc=andy.koppe@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=martinvonz@google.com \
    --cc=peff@peff.net \
    --cc=ps@pks.im \
    --cc=remo@buenzli.dev \
    /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).