From: Leo Famulari <leo@famulari.name>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add tintin.
Date: Fri, 19 Aug 2016 15:15:08 -0400 [thread overview]
Message-ID: <20160819191508.GB16782@jasmine> (raw)
In-Reply-To: <CAL1_imktWW3QnF=4_jEtaVjDdzU6JGbK-in_t0qQtYLA5OOsgg@mail.gmail.com>
On Fri, Aug 19, 2016 at 11:48:51AM +0200, David Craven wrote:
> > I usually attach the patches as files, in notmuch emacs they are saved
> > by pressing
> > . s
> > when in the displayed attached files part. Or what exactly do you mean?
>
> Yep that's what I mean. I'm currently doing this:
> Look at the patch in gmail
> touch 0.patch
> copy paste the email into 0.patch
> git am 0.patch
> copy paste again because I didn't copy the right part
> git am 0.patch
I was lucky to already be comfortable in Mutt when I started helping
with Guix. Mutt can run shell commands with the current message as
stdin, so I invoke that mode and do `cd ~/guix && git am` and everything
works, assuming the patch is okay.
It would be really painful if I had to use something in a web browser,
like gmail.
next prev parent reply other threads:[~2016-08-19 19:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 20:00 [PATCH] Add tintin ng0
2016-08-08 20:12 ` ng0
2016-08-08 21:13 ` ng0
2016-08-08 21:21 ` ng0
2016-08-19 9:01 ` ng0
2016-08-19 9:21 ` David Craven
2016-08-19 9:38 ` ng0
2016-08-19 9:48 ` David Craven
2016-08-19 10:30 ` ng0
2016-08-19 11:25 ` David Craven
2016-08-19 11:50 ` Marius Bakke
2016-08-19 12:38 ` David Craven
2016-08-19 17:59 ` David Craven
2016-08-19 18:46 ` Marius Bakke
2016-08-19 19:15 ` Leo Famulari [this message]
2016-08-20 16:38 ` Alex Vong
2016-08-20 17:18 ` David Craven
2016-08-23 17:05 ` David Craven
2016-08-23 22:31 ` ng0
2016-08-23 23:00 ` David Craven
2016-08-24 8:35 ` Question about emacs and guix (was: Re: [PATCH] Add tintin) Alex Kost
2016-08-19 19:32 ` [PATCH] Add tintin Leo Famulari
2016-08-19 20:40 ` ng0
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=20160819191508.GB16782@jasmine \
--to=leo@famulari.name \
--cc=david@craven.ch \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).