From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb <gdb@sources.redhat.com>, Jim Blandy <jimb@redhat.com>,
Fernando Nasser <fnasser@redhat.com>
Subject: Re: [rfc] plans for linespec.c
Date: Wed, 08 Jan 2003 22:48:00 -0000 [thread overview]
Message-ID: <ro1u1gjcl7i.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <15900.13786.731656.596183@localhost.redhat.com>
On Wed, 8 Jan 2003 09:29:46 -0500, Elena Zannoni <ezannoni@redhat.com> said:
> David Carlton writes:
>> So what makes sense for me to do is:
>> 1) Start doing some obvious patches that only do stuff like change
>> formatting, rename variables, etc.; unless Elena or somebody else
>> objects, I'll post these to gdb-patches but I won't wait for
>> approval, since they clearly won't change GDB's behavior.
> This is ok, as long as the patches are simple. I.e. better have more
> smaller patches, rather than a big one. But you know this already!
Great, I'll make sure to keep those patches small.
>> 2) Start submitting a series of patches to break up decode_compound
>> and functions that it calls into smaller functions, just like I've
>> been doing with decode_line_1. These will, of course, require
>> approval.
>> Once all that's done, I'll then get back to cleaning up decode_line_1
>> some more.
>> How does that sound?
> Sounds good.
Okay, it's a plan, then.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-01-08 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 22:22 David Carlton
2003-01-08 14:25 ` Elena Zannoni
2003-01-08 22:48 ` David Carlton [this message]
2003-01-08 0:12 Michael Elizabeth Chastain
2003-01-08 23:22 ` David Carlton
2003-01-09 4:24 Michael Elizabeth Chastain
2003-01-09 6:01 ` David Carlton
2003-01-09 9:45 ` Joel Brobecker
2003-01-09 16:09 Michael Elizabeth Chastain
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=ro1u1gjcl7i.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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