From: Leo Famulari <leo@famulari.name>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Question about sending in patches
Date: Wed, 14 Apr 2021 21:08:56 -0400 [thread overview]
Message-ID: <YHeSKCecCRSgkA9T@jasmine.lan> (raw)
In-Reply-To: <fb647b77-23e1-ff00-c17b-1d7c88fb8dd3@posteo.de>
On Thu, Apr 15, 2021 at 01:11:13AM +0200, Zelphir Kaltstahl wrote:
> A while ago I sent in a patch to add a package, but I realize, that I might have
> made a mistake, by attaching the git patch file, instead of copy pasting its
> content as a message.
>
> Should I send a new patch with the patch as the only text in the e-mail?
No, the attachment is totally fine. However you get your code submitted
is good enough.
It may actually be more reliable to use an attachment, rather than
copying and pasting.
next prev parent reply other threads:[~2021-04-15 1:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 23:11 Question about sending in patches Zelphir Kaltstahl
2021-04-15 1:08 ` Leo Famulari [this message]
2021-04-16 18:22 ` Adriano Peluso
2021-04-16 18:58 ` Zelphir Kaltstahl
2021-04-16 14:01 ` Joshua Branson
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=YHeSKCecCRSgkA9T@jasmine.lan \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).