Eric, I have submitted patch version 5 to fix the issue that you are concerned, hope you can have a review this series of patches, thanks.
Result: 250 2.6.0 <1499825297-20335-1-git-send-email-gengdong...@huawei.com> [InternalId=34134279] Queued mail for delivery Result: 250 2.6.0 <1499825297-20335-2-git-send-email-gengdong...@huawei.com> [InternalId=34134285] Queued mail for delivery Result: 250 2.6.0 <1499825297-20335-3-git-send-email-gengdong...@huawei.com> [InternalId=34134289] Queued mail for delivery Result: 250 2.6.0 <1499825297-20335-4-git-send-email-gengdong...@huawei.com> [InternalId=34134294] Queued mail for delivery On 2017/7/11 21:58, Eric Blake wrote: > On 07/11/2017 08:43 AM, Laszlo Ersek wrote: >> So send the patches with >> >> git send-email *.patch >> >> or put all the patches into a temporary directory, and run >> >> git send-email patch-dir/ > > Or you can even skip patch files, and directly send things with one lass > chance in your editor: > > git send-email -v5 -3 --annotate --cover-letter > > [send the top three commits in my current git branch as a version 5 > patch series, where I get to write the cover letter and tweak any of the > patches in my preferred $EDITOR before sending anything] >
