diff options
| author | Kyle Meyer <kyle@kyleam.com> | 2022-07-09 02:45:14 -0400 |
|---|---|---|
| committer | Kyle Meyer <kyle@kyleam.com> | 2022-07-10 10:19:44 -0400 |
| commit | 6776cacf0e524389d8177df7e295ea38e7116a73 (patch) | |
| tree | fd0b92ad245c5c9defdc163741baeea67ad38e7a /post-applypatch | |
| parent | 67411fadab680b01d9027a3f4833ef8892377874 (diff) | |
| download | piem-6776cacf0e524389d8177df7e295ea38e7116a73.tar.gz | |
piem-am: Order attached patches by file name prefix
When extracting patches from attachments, piem-gnus-am-ready-mbox and
piem-notmuch-am-ready-mbox construct the mbox messages in the same
order as the attachments. This depends on the sender attaching the
patches in ascending order.
Be a bit more helpful in situations where the sender attaches the
patches out of order by reordering patches according to the NNNN-
prefix that git-format-patch adds to the start of the patch file name.
This approach won't be able to reliably sort patches that aren't
generated by git-format-patch, but that's outside of any use case that
piem is intended to support.
Suggested-by: Ihor Radchenko <yantar92@gmail.com>
Link: https://inbox.kyleam.com/piem/87mtdj9dzt.fsf@localhost
Message-Id: <878rp2pyx1.fsf@kyleam.com>
Diffstat (limited to 'post-applypatch')
0 files changed, 0 insertions, 0 deletions