[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMP44s2oYm+iE-BYu93-bniTRPiu_LZWSAmAd8xEoNSZJbjemQ@mail.gmail.com>
Date: Fri, 2 Aug 2013 12:56:09 -0500
From: Felipe Contreras <felipe.contreras@...il.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Aaron Lu <aaron.lwe@...il.com>, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, Len Brown <lenb@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Jiri Kosina <trivial@...nel.org>
Subject: Re: [PATCH 2/3] acpi: video: trivial style cleanups
On Fri, Aug 2, 2013 at 9:09 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Thursday, August 01, 2013 11:18:34 PM Felipe Contreras wrote:
>> On Thu, Aug 1, 2013 at 8:55 PM, Aaron Lu <aaron.lwe@...il.com> wrote:
>> > On 08/02/2013 07:44 AM, Felipe Contreras wrote:
>> >> Signed-off-by: Felipe Contreras <felipe.contreras@...il.com>
>> >
>> > Change log please.
>>
>> You mean a commit message?
>
> No. He meant the part that goes between the subject and the signoff.
> This is called a change log (or changelog).
Not in Git lingo.
% man git commit
"Though not required, it’s a good idea to begin the commit message
with a single short (less than 50 character) line summarizing the
change, followed by a blank line and then a more thorough
description."
>> That's what it's called in Git lingo, and
>> it's right there:
>>
>> acpi: video: trivial style cleanups
>
> And that's not sufficient, because it doesn't explain *what* cleanups are
> being made.
Yes it does; *style* cleanups (coding-style).
--
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists