[linux-cifs-client] Re: linux-cifs workflow and git trees (was: cp -p localfile to a winnt, w2k0, winxp server - and legacy servers)

[Steve French]

git-format-patch with no options is fine with me (but not all patch
submitters are using git - I am not sure what is easiest for them),
This form saves time since it eliminates the steps of having to set
and then reset environment variables and avoids having to cut/paste
the commit description (and it also puts a more realistic changeset
date) - and by attaching the patch as an attachment to email it makes
it easier when I read gmail via the web (since the browser/gmail
modifying tabs/whitespace in the web email affects inline patches)

On Sat, Aug 2, 2008 at 8:07 PM, Jeff Layton <jlayton at redhat.com> wrote:
> On Sat, 2 Aug 2008 12:28:27 -0500
> "Steve French" <smfrench at gmail.com> wrote:
>
>> On Sat, Aug 2, 2008 at 6:04 AM, Jeff Layton <jlayton at redhat.com> wrote:
>> > I also don't envy Steve's task, which is why I'd like to see us use the
>> > tools to make it easier for him...
>> The biggest two things that would help me are simple a) all patches in
>> "git-am" form
>> so I can apply them immediately if the review passes
>
> By "git-am form", I presume you mean that you want us to generate the
> patches with "git-format-patch"? Any particular flags you want us to
> use when generating these patches?
>
> --
> Jeff Layton <jlayton at redhat.com>
>



-- 
Thanks,

Steve