From: Christopher Baines <mail@cbaines.net>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix@gnu.org
Subject: Re: Workflow with mu4e + magit for sending patchsets to guix?
Date: Mon, 16 Nov 2020 20:48:18 +0000 [thread overview]
Message-ID: <87eektm3jh.fsf@cbaines.net> (raw)
In-Reply-To: <87ima5f3mi.fsf@dustycloud.org>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Christopher Lemmer Webber <cwebber@dustycloud.org> writes:
> 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.
I think git send-email on the command line does the right thing.
For a single patch, I just git send-email --to=guix-patches@gnu.org
HEAD^
For a series of patches, it's more drawn out. First I run git
format-patch --cover-letter ... then copy the cover letter in to an
email, and then send to guix-patches@gnu.org. Then I wait for the
reply, and then git send-email --to=NUMBER@debbugs.gnu.org
--in-reply-to=MESSAGE ID FROM THE FIRST EMAIL.
I'm not sure if the --in-reply-to bit is useful.
I do use mu4e and magit myself, but I'm not sure I know a way of sending
patches more quickly or more easily than this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-11-16 20:48 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 [this message]
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
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=87eektm3jh.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
/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.