From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA, doc RFA] Add "set debug symfile on".
Date: Wed, 25 Sep 2013 21:03:00 -0000 [thread overview]
Message-ID: <CADPb22TeAtou=eE9fEwPyYB_vvUrnGcnp6Wc1Y_r7fb+_7=qHA@mail.gmail.com> (raw)
In-Reply-To: <87fvssisi8.fsf@fleche.redhat.com>
On Wed, Sep 25, 2013 at 12:57 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> This patch adds a new debugging option: set debug symfile on
>
> Doug> For now it logs all calls through the symfile functions.
>
> Doug> Regression tested on amd64-linux.
>
> Doug> Ok to check in?
>
> It seems ok to me.
>
> This patch combines a few different things into one. For example,
> reordering the arguments to map_matching_symbols has no relation to the
> rest of the patch. We normally make other contributors split such
> patches. I think it is best if maintainers do this as well.
I realize that. [And I figured you'd bring it up. :-)]
My argument is that for a small patch of this approx size I don't want
to impose on contributors *always* having to follow this rule.
One can reasonably counter with how can one know what the threshold
is, and that it would be more consistent to just always follow this
rule.
I guess this is one case where I'm a bit more wishy washy - it's a
time saver (and that's important!).
[As for time spent by the reviewer: for small enough patches any
incremental time is negligible IMO.]
To be clear, for larger patches I would indeed follow this rule (when
I remember to ... 1/2 :-)).
But no matter. I'll put in the time to split it up and check it in that way.
prev parent reply other threads:[~2013-09-25 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 0:25 Doug Evans
2013-09-25 0:31 ` Doug Evans
2013-09-25 5:57 ` Eli Zaretskii
2013-09-25 19:57 ` Tom Tromey
2013-09-25 21:03 ` Doug Evans [this message]
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='CADPb22TeAtou=eE9fEwPyYB_vvUrnGcnp6Wc1Y_r7fb+_7=qHA@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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