From: Quentin Schulz <quentin.schulz@cherry.de>
To: "Jörg Sommer" <joerg.sommer@navimatix.de>
Cc: docs@lists.yoctoproject.org
Subject: Re: [PATCH] doc/features: describe distribution feature pni-name
Date: Mon, 2 Sep 2024 12:40:54 +0200 [thread overview]
Message-ID: <71c085db-d16d-4d60-a489-28d56bc07bbb@cherry.de> (raw)
In-Reply-To: <jxpkr6zfcyhqattfqxvafzkzfiouoicvnpwdgtacztrfdodb4a@smhc47c3enzb>
Hi Jörg,
On 9/2/24 10:59 AM, Jörg Sommer wrote:
> Quentin Schulz schrieb am Mo 02. Sep, 10:42 (GMT):
>> Hi Jörg,
>>
>> Please try to add the v2 when sending the second version of a patch so the
>> maintainer doesn't have to guess which one is the latest from their inbox.
>
> Yes, you're right. I've realised it the moment git-send-email printed the
> subject.
>
>> Also try to add below the --- what changed between v1 and v2.
>
> Is there a git-send-email option to do so easily?
>
Not that I'm aware. I used to use git-format-patch and then edit the
patches by hand if I remember correctly. I've personally switched to
b4[1] about 2 years ago for my contributions to different projects and
the diff between versions is stored in the cover-letter, which is stored
as an empty commit on top of your series. If there's only one patch in
the series, the content of the cover-letter is added below the --- of
the patch.
[1] https://b4.docs.kernel.org/en/latest/contributor/overview.html
Cheers,
Quentin
next prev parent reply other threads:[~2024-09-02 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 11:40 [PATCH 1/2] doc/features: describe distribution feature pni-name Jörg Sommer
2024-08-30 11:40 ` [PATCH 2/2] doc/features: remove duplicate word in distribution feature ext2 Jörg Sommer
2024-08-30 12:21 ` [docs] " Quentin Schulz
2024-08-30 12:19 ` [docs] [PATCH 1/2] doc/features: describe distribution feature pni-name Quentin Schulz
2024-08-30 12:26 ` Jörg Sommer
2024-08-31 7:14 ` [PATCH] " Jörg Sommer
2024-09-02 8:42 ` Quentin Schulz
2024-09-02 8:59 ` Jörg Sommer
2024-09-02 10:40 ` Quentin Schulz [this message]
2024-09-03 8:33 ` [docs] " Alexandre Belloni
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=71c085db-d16d-4d60-a489-28d56bc07bbb@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=docs@lists.yoctoproject.org \
--cc=joerg.sommer@navimatix.de \
/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