From: Florian Mickler <florian@mickler.org>
To: Greg KH <greg@kroah.com>
Cc: Hank Janssen <hjanssen@sailtheuniverse.com>,
hjanssen@microsoft.com, Haiyang Zhang <haiyangz@microsoft.com>,
devel@driverdev.osuosl.org, virtualization@lists.osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: hv: Remove camel case variables in channel.c
Date: Tue, 5 Oct 2010 09:23:19 +0200 [thread overview]
Message-ID: <20101005092319.7ae2ba86@schatten.dmk.lab> (raw)
In-Reply-To: <20100930121210.GA14358@kroah.com>
On Thu, 30 Sep 2010 05:12:10 -0700
Greg KH <greg@kroah.com> wrote:
> On Wed, Sep 29, 2010 at 09:21:50PM -0700, Hank Janssen wrote:
> >
> > Rename camel case variables in channel.c and changed them to
> > lowercase.
> >
> > Sending this from my own accounts till we have a proper mail server
> > set up that allows us to send out patches without issues.
>
> This paragraph goes below the '---' line, it doesn't belong in the
> change log, right?
I recently read something about 'scissor lines' which allow more
natural reading flow with patches by git automatically skipping
everything above a scissor-line:
'A line that mainly consists of scissors (either ">8" or "8<") and
perforation (dash "-") marks is called a scissors line'
man git-mailinfo
git-am -c
:-)
Cheers,
Flo
next prev parent reply other threads:[~2010-10-05 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 4:21 [PATCH 1/1] staging: hv: Remove camel case variables in channel.c Hank Janssen
2010-09-30 12:12 ` Greg KH
2010-10-05 7:23 ` Florian Mickler [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-30 17:52 Hank Janssen
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=20101005092319.7ae2ba86@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=hjanssen@sailtheuniverse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.