[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPNrq4zHhhOp81B=a330Kst1Qwu2HWevRkS6KN9400zvq=W_Sw@mail.gmail.com>
Date: Fri, 20 Jan 2017 16:54:06 +0530
From: "Gideon D'souza" <gidisrael@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: kbuild test robot <lkp@...el.com>,
"kbuild-all@...org" <kbuild-all@...org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg Ungerer <gerg@...ux-m68k.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: [PATCH 2/2] m68k: replaced gcc specific macros with ones from compiler.h
Ah I didn't know they would be tracked a series. Should I resend these?
On Fri, Jan 20, 2017 at 4:04 PM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> Hi Gideon,
>
> On Fri, Jan 20, 2017 at 11:21 AM, Gideon D'souza <gidisrael@...il.com> wrote:
>>> Gideon: what exactly did you use to send this email series?
>> I used git format-patch and then send-email on my Fedora 24 system.
>>
>> I did :
>>
>> git format-patch HEAD^^ # this generated two patches for the two commits I made
>> git send-email --to ... ~/patches/0001- .... #sent first patch
>> git send-email --to ... ~/patches/0002- ....#sent second patch
>>
>> Yes, I sent each patch individually. Should I have just passed the directory?
>
> You should pass all patches at once, so they are properly tracked as a
> series:
>
> git send-email --to ... ~/patches/0*
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
Powered by blists - more mailing lists