Hi,
On Tue, 17 Nov 2020 at 23:55, Kyle Meyer <k...@kyleam.com> wrote:
>>>> 4. !! send-email --to=guix-patc...@gnu.org 0000-cover-letter.patch
>>>> 5. Wait and refresh my inbox
>>>> 6. !! send-email --to=12...@gnu.org 000?-*.patch
[...]
>> To me, today the main annoyance is the selection of the patches at the
>> step #6. For example, avoid to resend unrelated patches, as:
[...]
> Yeah, I agree about that being the most annoying aspect, but I'd say
> that core problem comes from the need for a two-step send. That's a
> quirky enough divergence from the standard workflow that I think any
> solution/helper here is unlikely to be in the scope of Magit. But that
> doesn't mean I don't think it'd be nice to come up with a helper.
[...]
> As I said, I'm not sold on this being something that fits Magit proper,
> but I'll help write a helper :)
Instead of Magit, maybe the helper should be in Emacs-Guix.
> Here's a command that gets you close to that layout. It adds an
> additional "<name>/" directory on top of the structure you show above.
> The name is reads from the caller (with a default completion value of
> the current branch name). It also depends on the caller having an
> upstream branch set (which I think is a good thing), but you could
> rework it to avoid it.
>
> --8<---------------cut here---------------start------------->8---
> (defun my/magit-patch-create-split-directory (name &optional args files)
> "Create patches in a split layout.
Awesome! Thank you. I am going to add to my config and see how it is
going. :-)
> (transient-append-suffix 'magit-patch-create "c"
> '("s" "Split directory" my/magit-patch-create-split-directory))
> --8<---------------cut here---------------end--------------->8---
Yeah, you are right, it seems better that way than being part of Magit
proper.
Thanks,
simon
