From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: Hank Janssen <hjanssen@microsoft.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Staging: hv: Add proper versioning to HV drivers-Corrected.
Date: Fri, 12 Feb 2010 11:39:44 -0800 [thread overview]
Message-ID: <43e72e891002121139y4bb4fbc2mdfc99f3b7ad6ebef@mail.gmail.com> (raw)
In-Reply-To: <20100212184756.GA14751@suse.de>
On Fri, Feb 12, 2010 at 10:47 AM, Greg KH <gregkh@suse.de> wrote:
> On Fri, Feb 12, 2010 at 05:55:34PM +0000, Hank Janssen wrote:
>>
>> > >
>> > > drivers/staging/hv/VersionInfo.h | 22 +++++++++++++++++++---
>> >
>> > You forgot a "---" between the signed-off-by and the diffstat. If you
>> > use either git or quilt, it will get this correct automagically. That
>> > infers you used something else, which is quite scary. What are you
>> > using instead to create patches?
>> >
>> > Don't worry, I can edit this by hand when I apply it, and will do so in
>> > a few days when I get to my "to-apply" queue, but in the future, please
>> > don't do this.
>> >
>> > thanks,
>> >
>> > greg k-h
>>
>> This must have been the result of a cut/paste error on my side.
>>
>> I use the following command for my diff 'git diff -M -u --stat'
>
> What's wrong with 'git format-patch'?
>
> You are creating a "raw" diff, which is fine, but you then need to
> include the rest of the comments. If you commit the patch to a branch,
> with the comments in them, then you can just automatically create the
> patches in correct format.
In case this helps:
http://wireless.kernel.org/en/developers/Documentation/git-guide
Toward s the end there is a git format-patch blurb and explains how to
set up your e-mail client with ssmpt.
Luis
prev parent reply other threads:[~2010-02-12 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 23:02 Hank Janssen
2010-02-11 23:36 ` Greg KH
2010-02-12 17:55 ` Hank Janssen
2010-02-12 18:47 ` Greg KH
2010-02-12 19:39 ` Luis R. Rodriguez [this message]
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=43e72e891002121139y4bb4fbc2mdfc99f3b7ad6ebef@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®