unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: help-guix@gnu.org
Subject: Re: Workflow with mu4e + magit for sending patchsets to guix?
Date: Wed, 18 Nov 2020 09:17:44 +0100	[thread overview]
Message-ID: <86blfvm63b.fsf@gmail.com> (raw)
In-Reply-To: <87eekr461w.fsf@kyleam.com>

Hi,

On Tue, 17 Nov 2020 at 23:55, Kyle Meyer <kyle@kyleam.com> wrote:

>>>>  4. !! send-email --to=guix-patches@gnu.org 0000-cover-letter.patch
>>>>  5. Wait and refresh my inbox
>>>>  6. !! send-email --to=12345@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


  reply	other threads:[~2020-11-18  8:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 20:28 Workflow with mu4e + magit for sending patchsets to guix? Christopher Lemmer Webber
2020-11-16 20:48 ` Christopher Baines
2020-11-16 23:49 ` zimoun
2020-11-17  2:36   ` Kyle Meyer
2020-11-17  7:28     ` Pierre Neidhardt
2020-11-17 14:10       ` zimoun
2020-11-25  9:19         ` Pierre Neidhardt
2020-11-25 12:33           ` zimoun
2020-11-26  9:51             ` Pierre Neidhardt
2020-11-30 22:30               ` Kyle Meyer
2020-12-01  9:10                 ` Pierre Neidhardt
2020-12-01 16:26                   ` zimoun
2020-11-17 15:01     ` zimoun
2020-11-18  4:55       ` Kyle Meyer
2020-11-18  8:17         ` zimoun [this message]
2020-11-17 15:39     ` 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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86blfvm63b.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=kyle@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.
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).