From: "Mark Ryden" <markryde@gmail.com>
To: git@vger.kernel.org
Subject: Applying patches from a patch set
Date: Sat, 20 Dec 2008 16:37:42 +0200 [thread overview]
Message-ID: <dac45060812200637m49c71aa5x3c25010fa00f4a63@mail.gmail.com> (raw)
Hello,
I am subscribed to some linux kernel subsystem mailing list; in this
list there are sometimes patchsets with more than
30-40 patches.
I am using gmail web interface client.
In order to apply a patch set I copy and paste each patch from the
patchset into a file, and then apply that patch.
I assume that there is a better way.
Recently I encountered a fatal error when doing so (and I am not sure
what caused it).
So my question is: does anyone know a more elegant way of applying a
large patchset ?
Maybe there is better mail client with which this process can be done easily ?
(I remember there was something called git apply-mbox in the past).
Rgs,
Mark
next reply other threads:[~2008-12-20 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 14:37 Mark Ryden [this message]
2008-12-20 19:25 ` Applying patches from a patch set Jakub Narebski
2008-12-20 20:06 ` Junio C Hamano
2008-12-23 11:25 ` Mark Ryden
2008-12-21 8:20 ` Sitaram Chamarty
2008-12-21 18:34 ` Mark Ryden
2008-12-21 18:53 ` Jakub Narebski
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=dac45060812200637m49c71aa5x3c25010fa00f4a63@mail.gmail.com \
--to=markryde@gmail.com \
--cc=git@vger.kernel.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.
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).