From: Pierre Neidhardt <mail@ambrevar.xyz>
To: John Soo <jsoo1@asu.edu>,
Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix@gnu.org
Subject: Re: Nicest way to send and apply Guix patchsets via magit?
Date: Sat, 22 Aug 2020 12:45:04 +0200 [thread overview]
Message-ID: <87pn7jgdsf.fsf@ambrevar.xyz> (raw)
In-Reply-To: <2FD11C17-9ECA-4843-BC70-69693901D46B@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
For me, "git send-email" unpredictably drops some patches without
notice. I don't know if it's a bug with our package or with upstream.
About Magit, I'd also recommend to "insert base commit" when creating
the patchset. Something like "W c C-m b ... c".
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-08-22 10:45 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
2020-08-22 10:45 ` Pierre Neidhardt [this message]
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=87pn7jgdsf.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=jsoo1@asu.edu \
/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).