This is the mail archive of the
mailing list for the glibc project.
Re: redundant ChangeLog header lines
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Wed, 16 May 2012 23:01:30 -0400
- Subject: Re: redundant ChangeLog header lines
- References: <20120516223630.C0E1C2C0BC@topped-with-meat.com>
On Wed, May 16, 2012 at 6:36 PM, Roland McGrath <email@example.com> wrote:
> When you're adding a new log entry and the header line (the one with
> the date and your name) would be identical to the existing top header
> line in the file, then don't add a new header line. ?The header lines
> are only there to show when the information they contain (date, name,
> email) differs from the previous entry (i.e. the one immediately
> following in the file).
> Two logically-separate changes are indicated just by being in two
> different paragraphs (i.e. having a blank line between them). ?When
> you do a bunch of changes that all go together (in one commit--because
> they are logically related and you can't build successfully with one
> and not the other), you should not have blank lines in the middle of
> the log entries for all those changes.
Could you please document this in the commiters checklist?
I had no clue it actually worked the way that you describe.
I just thought some people were lazy...