Question about applying a kernel patch with "git am" received from a mailing list

[Kevin Wilson]

Hi, Josh,

Thanks again!

While your suggestion works, it has some disadvantages; maybe
you/someone can advice:

1) In the case when I want to apply a series of patches, let's say a
patchset of 10 patches, does this mean that I should run
"pipe git am" on each of them ?

2) Even this is the case; suppose I apply 10 patches. Then I
make some tests, and want to return to the original tree,  (by git
reset --hard) and after a day or say again apply these patches (or
some of them) I should go into mutt, browse the list of messages and
find them,  and then apply them, etc...


Is there no way to save patches and then "git am" the patches
without these error ? I heard that mutt is very popular
for working with patches. Such a feature seems natural to me.

rgs
Kevin

On Tue, Nov 20, 2012 at 8:02 PM, Josh Cartwright <joshc at eso.teric.us> wrote:
> 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 at 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