From: Ihor Radchenko <yantar92@gmail.com>
To: piem@inbox.kyleam.com
Subject: [BUG] Patch order is not respected for sequence of patches like [PATCH X/Y]
Date: Sat, 09 Jul 2022 11:11:34 +0800 [thread overview]
Message-ID: <87mtdj9dzt.fsf@localhost> (raw)
Hi,
I just tried to use piem for patches in
https://orgmode.org/list/87v8s8n1bm.fsf@heagren.com
The patches are supposed to be applied in specific order 1/2 and then
2/2. However, the patches in the email are attached in the opposite
order.
piem-am on the above email disregards the patch order and simply applies
the patches as they appear in the email attachments, which is not what
the patch author intended.
I consider the current behavior a bug.
Best,
Ihor
next reply other threads:[~2022-07-09 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 3:11 Ihor Radchenko [this message]
2022-07-09 6:45 ` [PATCH] piem-am: Order attached patches by file name prefix Kyle Meyer
2022-07-09 7:38 ` Ihor Radchenko
2022-07-09 16:56 ` Kyle Meyer
2022-07-10 9:59 ` Ihor Radchenko
2022-07-10 14:25 ` Kyle Meyer
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
List information: https://git.kyleam.com/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtdj9dzt.fsf@localhost \
--to=yantar92@gmail.com \
--cc=piem@inbox.kyleam.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.kyleam.com/piem/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).