From: joshc@eso.teric.us (Josh Cartwright)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Question about applying a kernel patch with "git am" received from a mailing list
Date: Tue, 20 Nov 2012 12:02:37 -0600 [thread overview]
Message-ID: <20121120180237.GE6280@kryptos> (raw)
In-Reply-To: <CAGXs5wW49Y2uQhW=PYc=tR4CaG=FwcYv=-hjxtK2BUDvAv-foA@mail.gmail.com>
On Tue, Nov 20, 2012 at 07:53:57PM +0200, Kevin Wilson wrote:
> On Tue, Nov 20, 2012 at 7:39 PM, Josh Cartwright <joshc@eso.teric.us> wrote:
> > On Tue, Nov 20, 2012 at 07:24:28PM +0200, Kevin Wilson wrote:
> > > Hi,
> > > I am following some kernel mailing lists (netdev and others).
> > > I want to be able to save recent patches and to apply the against a git tree.
> > >
> > > I tried using MUTT client for this. I save the patch (which is almost
> > > always inline).
> > >
> > > Then I run
> > > git apply --check patchName
> > > and
> > > git apply patchName
> > > and it applies cleanly.
> > >
> > > But if I try:
> > > git am patchName
> > >
> > > It gives
> > > "Patch format detection failed."
> > >
> > > Any recommendation what to do to apply a patch
> > > with "git am"?
> >
> > Kevin-
> >
> > Just use mutt's 'pipe-message' feature, which is bound to '|' by
> > default. Pipe the message directly to 'git am'.
>
> Hi,
> Thanks for the quick response! I press "|" , I want to pipe to the
> git tree (which is /work/src/net-next). How do I tell pipe that the
> path of git tree is there?
Simple!
Instead of piping to 'git am', pipe to 'cd /work/src/net-next && git am'.
Alternatively, run mutt from your source tree.
Josh
next prev parent reply other threads:[~2012-11-20 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 17:24 Question about applying a kernel patch with "git am" received from a mailing list Kevin Wilson
2012-11-20 17:39 ` Josh Cartwright
2012-11-20 17:53 ` Kevin Wilson
2012-11-20 18:02 ` Josh Cartwright [this message]
2012-11-21 14:05 ` Kevin Wilson
2012-11-21 18:56 ` Jonathan Neuschäfer
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=20121120180237.GE6280@kryptos \
--to=joshc@eso.teric.us \
--cc=kernelnewbies@lists.kernelnewbies.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).