Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org,
	Andrey Smirnov <andrew.smirnov@gmail.com>,
	Marek Polacek <mpolacek@redhat.com>
Subject: Re: [PATCH 22/348] Fix -Wsahdow warnings
Date: Tue, 22 Nov 2011 16:20:00 -0000	[thread overview]
Message-ID: <201111221120.06244.vapier@gentoo.org> (raw)
In-Reply-To: <20111122160539.GA22283@adacore.com>

[-- Attachment #1: Type: Text/Plain, Size: 1153 bytes --]

On Tuesday 22 November 2011 11:05:39 Joel Brobecker wrote:
> > please condense down your patches if you resend.  there's way too many
> > little tiny ones that really should be squashed into a single
> > changeset.
> 
> In my view, if the patches can be checked in independently, then
> it is a good thing that they are split. Imagine the situation where
> one of these changes is bad, we'd then be able to revert that one
> patch, rather than fixing by hand.

i'm not saying it should be exactly 1 patch.  but 348 is way too big.  doing 
it on an API or file level is a good compromise.

> > your ChangeLogs are also incorrect.  it should not be:
> > 	* bcache.c (expand_hash_table): Fix -Wshadow warnings.
> > 
> > but rather:
> > 	* bcache.c (expand_hash_table): Rename bcache to cache.
> 
> I'm 50/50 on this. I don't mind either way. What do others think?
> Is that really that important that we must create boring extra work
> for Andrey?

it's my understanding that the GNU changelog style is "document what changed" 
and not "why".  i think that's largely stupid, but i'm not the one in control 
of said policy.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-11-22 16:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 13:07 Andrey Smirnov
2011-11-22 13:14 ` Eli Zaretskii
2011-11-22 13:34   ` Andrey Smirnov
2011-11-22 13:35     ` Marek Polacek
2011-11-22 14:04       ` Andrey Smirnov
2011-11-22 15:28         ` Mike Frysinger
2011-11-22 16:05           ` Joel Brobecker
2011-11-22 16:20             ` Mike Frysinger [this message]
2011-11-23 17:25               ` Doug Evans
2011-11-22 18:24             ` Tom Tromey
2011-11-23 16:46             ` Mark Kettenis
     [not found]               ` <CAHQ1cqFADK_pXv4JAW6ouvm_NPyM6dM+-FmVF0FojKi1rs98Wg@mail.gmail.com>
2011-11-24  3:23                 ` Andrey Smirnov
2011-11-23  5:29           ` Andrey Smirnov
2011-11-23 17:06             ` Tom Tromey
2011-11-24  3:18               ` Andrey Smirnov
2011-11-23 17:56             ` Doug Evans
2011-11-23 18:03               ` Doug Evans
2011-11-23 20:16                 ` Joel Brobecker
2011-11-24  4:33               ` Andrey Smirnov
2011-11-29 19:06                 ` Tom Tromey
2011-11-28 15:07         ` [PATCH 022/238] [misc.] bcache.c: -Wshadow fix Andrey Smirnov
2011-11-28 15:07           ` [PATCH 026/238] " Andrey Smirnov
2011-12-20 15:43             ` Tom Tromey
2011-11-28 15:07           ` [PATCH 024/238] " Andrey Smirnov
2011-12-20 15:46             ` Tom Tromey
2011-11-28 15:07           ` [PATCH 025/238] " Andrey Smirnov
2011-12-20 15:42             ` Tom Tromey
2011-12-20 15:42           ` [PATCH 022/238] " Tom Tromey
2011-12-20 16:13             ` Andrey Smirnov
2011-12-20 19:17               ` Tom Tromey
2011-12-20 19:31                 ` Andrey Smirnov
2011-12-20 21:06                   ` Tom Tromey

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=201111221120.06244.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=andrew.smirnov@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mpolacek@redhat.com \
    /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