Applying the same patch multiple times (was: [FR] Support multiple repositories associated with the same ML)

[Ihor Radchenko <yantar92@gmail.com>]

Kyle Meyer <kyle@kyleam.com> writes:

>   ;; TODO: Decide how to deal with inboxes that map to more than one
>   ;; coderepo.  This is important to support for people that want to
>   ;; use a catchall inbox for small projects which they don't think
>   ;; (yet) need a dedicated address.
>   (defcustom piem-inboxes nil
>
> I'll plan to take a look at this soon (within the next week or two).

Thanks!

I also noticed one minor annoyance when I return to work on the
previously applied patch.

My starting point is the patch-containing email. Then, I run piem-am and
use the default automatically generated branch.

Expected behaviour: Silently switch to the already existing branch
unless that branch had modifications to the patch in the email. In the
latter case, either throw an error or show the changes interactively.

Observed behaviour: Because the branch already exists and the patch is
already applied, git am throws an error.

I think a more useful approach would be something like:
1. piem creates a throwaway branch and apply the patch in the email
2. piem rebases the existing branch onto that throwaway branch

That way, I can start working on a patch from email, possibly add some
followup commits and still be able to return to this WIP branch starting
from the patch email.

Best,
Ihor