Calvin Wan [off-list ref] writes:
Original cover letter for context:
https://lore.kernel.org/git/20221011232604.839941-1-calvinwan@google.com/
Thanks. I'll try to take a look at this today.
By the way, how are you driving send-email when sending a
multi-patch series with a cover letter? It seems that all
messages in this series including its cover are marked as if they
are replies to the cover letter of the previous round, which is a
bit harder to follow than making only [v8 0/6] as a reply to [v7 0/X]
and all [v8 n/6] (n > 0) to be replies to [v8 0/6].
By the way, how are you driving send-email when sending a
multi-patch series with a cover letter? It seems that all
messages in this series including its cover are marked as if they
are replies to the cover letter of the previous round, which is a
bit harder to follow than making only [v8 0/6] as a reply to [v7 0/X]
and all [v8 n/6] (n > 0) to be replies to [v8 0/6].
I'll do that from now on -- didn't realize that make it harder to follow
On Thu, Feb 09 2023, Calvin Wan wrote:
quoted
By the way, how are you driving send-email when sending a
multi-patch series with a cover letter? It seems that all
messages in this series including its cover are marked as if they
are replies to the cover letter of the previous round, which is a
bit harder to follow than making only [v8 0/6] as a reply to [v7 0/X]
and all [v8 n/6] (n > 0) to be replies to [v8 0/6].
I'll do that from now on -- didn't realize that make it harder to follow
Welcome to the club :)
This came up before when I'd been sending mails like this for years,
without realizing the difference:
https://lore.kernel.org/git/nycvar.QRO.7.76.6.2103191540330.57@tvgsbejvaqbjf.bet/
& https://lore.kernel.org/git/xmqqr1k9k2w7.fsf@gitster.g/