From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] fix PR symtab/15597
Date: Thu, 10 Oct 2013 02:29:00 -0000 [thread overview]
Message-ID: <87iox5ame5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <21077.61952.984944.635448@ruffy.mtv.corp.google.com> (Doug Evans's message of "Wed, 9 Oct 2013 17:17:04 -0700")
Doug> So code was moved to a different file and edited in one step
Doug> (instead of moving it, and then editing it in a separate pass)?
In this case I thought it couldn't reasonably be moved verbatim, since,
IIRC, prior to my changes it required ELF bits from BFD, not allowed in
generic code.
Doug> [not that I mind per se, but I thought doing things that way
Doug> was more than just "nice to have"]
In your case the two changes had nothing to do with one another. I
think that is a reasonable standard. If you disagree, I'm sure we can
all agree on some other standard.
Tom
next prev parent reply other threads:[~2013-10-10 2:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 17:37 Tom Tromey
2013-08-10 5:36 ` Alan Modra
2013-08-12 8:41 ` Tom Tromey
2013-08-12 9:29 ` Alan Modra
2013-08-14 11:25 ` nick clifton
2013-10-08 19:38 ` Tom Tromey
2013-10-08 22:10 ` Hans-Peter Nilsson
2013-10-09 1:27 ` Tom Tromey
2013-10-09 14:09 ` Tom Tromey
2013-10-09 14:54 ` Build regression on 32-bit hosts [Re: [PATCH] fix PR symtab/15597] Jan Kratochvil
2013-10-09 15:46 ` Tom Tromey
2013-10-10 0:17 ` [PATCH] fix PR symtab/15597 Doug Evans
2013-10-10 2:29 ` Tom Tromey [this message]
2013-10-10 19:04 ` Doug Evans
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=87iox5ame5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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