From: Adriano Peluso <randomlooser@riseup.net>
To: Leo Famulari <leo@famulari.name>,
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Question about sending in patches
Date: Fri, 16 Apr 2021 20:22:50 +0200 [thread overview]
Message-ID: <919da4262449595ebd3d1a43b2ed3a0c395c2f78.camel@riseup.net> (raw)
In-Reply-To: <YHeSKCecCRSgkA9T@jasmine.lan>
Il giorno mer, 14/04/2021 alle 21.08 -0400, Leo Famulari ha scritto:
> It may actually be more reliable to use an attachment, rather than
> copying and pasting.
It was more reliable in my experience
At the time I was using a gmail account and when I pasted the text of
my patched in the body of an email, the text arrived mangled
I was overwhelmed by the git-send-mail thing so I attached my patches
for quite some time
of course the git-send-mail thing is more integrated but it's not a
strict requirement
next prev parent reply other threads:[~2021-04-17 4:52 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
2021-04-16 18:22 ` Adriano Peluso [this message]
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=919da4262449595ebd3d1a43b2ed3a0c395c2f78.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
--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).