From: Alyssa Ross <hi@alyssa.is>
To: Linus Heckemann <git@sphalerite.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] docs/devel: remove incorrect claim about git send-email
Date: Sat, 17 Sep 2022 07:12:57 +0000 [thread overview]
Message-ID: <87sfkqmq2u.fsf@alyssa.is> (raw)
In-Reply-To: <20220913165214.97241-1-git@sphalerite.org>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Linus Heckemann <git@sphalerite.org> writes:
> While it's unclear to me what git send-email actually does with the
> -v2 parameter (it is not documented, but also not rejected), it does
> not add a v2 tag to the email's subject, which is what led to the
> mishap in [1].
>
> [1]: https://lists.nongnu.org/archive/html/qemu-devel/2022-09/msg00679.html
It does for me!
Tested with:
git send-email -v2 --to hi@alyssa.is HEAD~
X-Mailer: git-send-email 2.37.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-09-17 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 16:52 [PATCH] docs/devel: remove incorrect claim about git send-email Linus Heckemann
2022-09-17 7:12 ` Alyssa Ross [this message]
2022-09-17 7:14 ` Alyssa Ross
2022-10-11 10:39 ` Linus Heckemann
2022-10-16 16:37 ` Alyssa Ross
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=87sfkqmq2u.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=git@sphalerite.org \
--cc=qemu-devel@nongnu.org \
/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.