From: John Soo <jsoo1@asu.edu>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix@gnu.org
Subject: Re: Nicest way to send and apply Guix patchsets via magit?
Date: Sun, 16 Aug 2020 09:34:09 -0700 [thread overview]
Message-ID: <2FD11C17-9ECA-4843-BC70-69693901D46B@asu.edu> (raw)
In-Reply-To: <87tux2379w.fsf@dustycloud.org>
Hi Christopher,
I usually use the log in Magit, highlight the commits I want and then use W c c to create a patch set. I submit them as attachments on one email usually (I use dired and gnus for that). I know threading (one patch per email) works better with tools like patchwork but I don’t want to drop to git send-mail.
One caveat is that I’m not sure how well my patch sets are received. I will accept any criticism there.
Curious to know how others work,
John
next prev parent reply other threads:[~2020-08-16 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 16:06 Nicest way to send and apply Guix patchsets via magit? Christopher Lemmer Webber
2020-08-16 16:34 ` John Soo [this message]
2020-08-22 10:45 ` Pierre Neidhardt
2020-08-22 12:12 ` Christopher Lemmer Webber
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=2FD11C17-9ECA-4843-BC70-69693901D46B@asu.edu \
--to=jsoo1@asu.edu \
--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.
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).