From: Mike Ralphson <mike.ralphson@gmail.com>
To: skillzero@gmail.com
Cc: "Wesley J. Landaker" <wjl@icecavern.net>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
git@vger.kernel.org, Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: How do gmail users try out patches from this list?
Date: Wed, 12 Aug 2009 09:43:37 +0100 [thread overview]
Message-ID: <e2b179460908120143j5b0eb964s666dd0d59c850db3@mail.gmail.com> (raw)
In-Reply-To: <4A827BF3.8080208@drmicha.warpmail.net>
2009/8/11 <skillzero@gmail.com>:
> Sorry if this is dumb question, but I didn't see any good info in my searches.
>
> How do gmail users normally apply patches that come through the list?
> Do you just manually copy and paste the email to patch files and use
> git apply? Do you use a tool to export to mbox files and use git am?
>
> I've been just doing it manually via copy and paste, but it's kinda tedious.
Yep, show original, copy and paste and git apply. Personally I would
prefer to fetch changes using, oh, I don't know, some kind of dvcs
tool... 8-) It means I don't tend to build and test many patch series
until they get merged.
It's a pity there's a patchwork server for many kernel.org projects,
but not for the git mailing list 8-(
http://patchwork.kernel.org/
http://patchwork.kernel.org/help/pwclient/
http://gitster.livejournal.com/18696.html
next prev parent reply other threads:[~2009-08-12 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 20:43 How do gmail users try out patches from this list? skillzero
2009-08-11 20:47 ` Emmanuel Trillaud
2009-08-11 20:55 ` Sverre Rabbelier
2009-08-11 21:24 ` Emmanuel Trillaud
2009-08-11 20:47 ` Russ Dill
2009-08-11 22:14 ` Nicolas Sebrecht
2009-08-12 1:17 ` Wesley J. Landaker
2009-08-12 8:23 ` Michael J Gruber
2009-08-12 8:43 ` Mike Ralphson [this message]
2009-08-12 13:43 ` Nguyen Thai Ngoc Duy
2009-08-12 12:51 ` Alex Riesen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2b179460908120143j5b0eb964s666dd0d59c850db3@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=nicolas.s.dev@gmx.fr \
--cc=skillzero@gmail.com \
--cc=wjl@icecavern.net \
/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 NNTP newsgroup(s).