Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	       gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 22/348] Fix -Wsahdow warnings
Date: Wed, 23 Nov 2011 17:06:00 -0000	[thread overview]
Message-ID: <m3mxbmydim.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAHQ1cqGuPPK7zMbb08Tbj2j6woqpDEBXXofeJzjN3F8qPZLgaQ@mail.gmail.com>	(Andrey Smirnov's message of "Wed, 23 Nov 2011 11:29:41 +0600")

>>>>> "Andrey" == Andrey Smirnov <andrew.smirnov@gmail.com> writes:

Andrey> Initially, there were 17 patches, which, upon suggestion from Tom
Andrey> Tromey, I split so that every patch contain only changes to one
Andrey> particular function or some other small unit of the source code. I
Andrey> tend to agree with Tom that my initial decision to make only 17
Andrey> patches made it rather hard to review each, because every one of them
Andrey> contained many small but disparate changes.

I didn't really mean for you to split it down this much, but now you've
done it.  I don't want to make too much extra work for you.

Andrey> Squashing or splitting commits is not really a problem and I can do
Andrey> this, but if you want me to do so, than please point out the patches
Andrey> I should squash together.

It is hard for us to do that without seeing the whole series :)

Conversely maybe it is hard for you to know which patches are likely to
be controversial and which are obvious.

I think it is hard to discuss in the abstract.  One idea would be for
you to merge reasonably obvious patches together in a file-based way,
using your best judgment about what "reasonably obvious" means.

Or, we can just carry on.

Andrey> So given the aforementioned amount of work, can't we ignore that the
Andrey> patch count is over 9000?

Not sure what this refers to.

Tom


  reply	other threads:[~2011-11-23 17:06 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
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 [this message]
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 025/238] " Andrey Smirnov
2011-12-20 15:42             ` Tom Tromey
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-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=m3mxbmydim.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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