all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>, help-guix@gnu.org
Cc: Kyle Meyer <kyle@kyleam.com>
Subject: Re: Workflow with mu4e + magit for sending patchsets to guix?
Date: Tue, 17 Nov 2020 00:49:19 +0100	[thread overview]
Message-ID: <86eeksq2v4.fsf@gmail.com> (raw)
In-Reply-To: <87ima5f3mi.fsf@dustycloud.org>

Hi Chris

+CC Kyle since they probably knows the status [1].

On Mon, 16 Nov 2020 at 15:28, Christopher Lemmer Webber <cwebber@dustycloud.org> wrote:

> I've been making patchset series of emails to guix-patches manually.
> I'm sure this is the wrong thing to do.  I use mu4e + magit and know
> others have a similar setup.
>
> What do you all do?

I am sending really few patches so my workflow is probably not
optimized.  What I do is from magit-status:

 1. Select the commits
 2. W c
    C-m b origin/master RET
    C-m l
    c
 3. Edit the cover letter
 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

Be careful if other patches remain in your current worktree.

Note base-commit which provides the information against which commit the
series applies.  It is really helpful for applying; especially if the
series falls in the crack *or* for the “new” tool b4 and the Emacs
front-end piem [2].  See thread here [3]. :-)


AFAIK, there is no ’send-email’ support with Magit.  I have never check
the built-in vc-mode.

What I have understood is that Magit-forge should implement ’send-email’
as a backend (forge) but it has not happened yet.  Or I missed the
news. :-)

I am curious to know how others Emacsers fellows do.


Hope that helps,
simon

1: <https://github.com/magit/magit/issues/2499>
2: <https://git.kyleam.com/piem/about/>
3: <https://yhetil.org/guix-patches/20201114003906.25111-1-kyle@kyleam.com>
4: <https://github.com/magit/magit/issues/1800>


  parent reply	other threads:[~2020-11-16 23:51 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=86eeksq2v4.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=cwebber@dustycloud.org \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.