From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] symbol hashing, part 2/n - ALL_BLOCK_SYMBOLS
Date: Fri, 12 Oct 2001 10:17:00 -0000 [thread overview]
Message-ID: <20011012131606.A16180@nevyn.them.org> (raw)
In-Reply-To: <15303.5958.839055.90447@krustylu.cygnus.com>
On Fri, Oct 12, 2001 at 12:16:06PM -0400, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
> > On Thu, Oct 11, 2001 at 07:54:50PM -0400, Daniel Jacobowitz wrote:
> > > On Thu, Oct 11, 2001 at 07:46:33PM -0400, Elena Zannoni wrote:
> > > >
> > > > Daniel,
> > > > Thanks so much for doing this. It makes it so much easier.
> > > >
> > > > Yes, I looked ths over and it seems to work, except that I would really
> > > > prefer the change to printcmd.c split in two. The first bit to
> > > > rationalize that "if (func)..." code. This would have with it all
> > > > the indentation changes as well. The code as it is now doesn't really
> > > > make much sense. So, that looks a good change to me. But it has nothing
> > > > to do with the new macro. After that change is in, you can introduce
> > > > the macro in printcmd.c w/o having all the indent changes.
> > > > It also makes it easier to distinguish a no-op change (the macro) from
> > > > the other one.
> > >
> > > OK. Would you prefer I resubmit this patch broken up further, then?
> > > I could do that.
> >
> > Having reduced it to truly obvious, I'm going to commit the attached
> > patch, unless someone objects strenuously in the near future. A diff
> > ignoring whitespace shows that I am only moving a brace from before a
> > for loop to after it; the for loop will never be executed unless the if
> > is taken, anyway. This'll shrink the other patch quite a bit.
> >
>
> Yes, thanks!!
So let it be written, etc. etc. Committed.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-10-12 10:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 9:35 Daniel Jacobowitz
2001-10-11 16:39 ` Elena Zannoni
2001-10-11 16:48 ` Daniel Berlin
2001-10-11 16:52 ` Elena Zannoni
2001-10-11 16:55 ` Daniel Jacobowitz
2001-10-11 17:43 ` Andrew Cagney
2001-10-11 17:48 ` Daniel Jacobowitz
2001-10-11 18:18 ` Andrew Cagney
2001-10-12 9:08 ` Elena Zannoni
2001-10-11 17:48 ` Daniel Berlin
2001-10-11 18:06 ` Andrew Cagney
2001-10-12 9:05 ` Elena Zannoni
2001-10-11 18:05 ` Daniel Jacobowitz
2001-10-12 9:09 ` Elena Zannoni
2001-10-12 10:17 ` Daniel Jacobowitz [this message]
2001-10-12 8:49 ` Elena Zannoni
2001-10-12 11:59 ` Daniel Jacobowitz
2001-10-12 13:03 ` Andrew Cagney
2001-10-12 15:34 ` Elena Zannoni
2001-10-12 16:53 ` Daniel Jacobowitz
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=20011012131606.A16180@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@cygnus.com \
--cc=gdb-patches@sources.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