[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 00/24] tree-wide spelling fixes
From: |
Michael Tokarev |
Subject: |
Re: [PATCH v2 00/24] tree-wide spelling fixes |
Date: |
Wed, 23 Aug 2023 09:26:41 +0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 |
This is interesting.
So, I forgot to remove old, already sent patches from the work dir
(usually I remove whole thing but didn't do that now). So I had
2 patch series in the same dir, one old already sent and applied,
and one new. And did git send-email series/* - which obviously
included both.
But the fun part is the References: headers and hence threading.
I used git format-patch --cover-letter $since-commit. Git created the
cover letter with Message-Id 20230823055155.1917375-1-mjt@tls.msk.ru.
And used this Id in References: header of the *first* patch.
But in all subsequent patches 2..24, it used *another* ID in the
References: header, the one taken from the *old* cover letter,
which it replaced when generating the new cover.
Obviously I did not edit the messages, did not specify anything
more fancy besides --cover-letter, - the only issue was that I
had another 4-file patch series in the same dir.
This smells like an.. interesting bug in git.. :)
/mjt
- [PATCH v2 00/24] tree-wide spelling fixes, Michael Tokarev, 2023/08/23
- [PATCH 01/24] block: spelling fixes, Michael Tokarev, 2023/08/23
- Re: [PATCH v2 00/24] tree-wide spelling fixes,
Michael Tokarev <=
- [PATCH 02/24] bsd-user: spelling fixes, Michael Tokarev, 2023/08/23
- [PATCH 03/24] ui: spelling fixes, Michael Tokarev, 2023/08/23
- [PATCH 04/24] util: spelling fixes, Michael Tokarev, 2023/08/23
- [PATCH 06/24] docs: spelling fixes, Michael Tokarev, 2023/08/23
- [PATCH 08/24] mips: spelling fixes, Michael Tokarev, 2023/08/23
- [PATCH 05/24] tcg: spelling fixes, Michael Tokarev, 2023/08/23