From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] convert blocks to dictionaries, phase 1, main part
Date: Tue, 17 Sep 2002 11:34:00 -0000 [thread overview]
Message-ID: <ro165x4fotl.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20020917174928.GA23058@nevyn.them.org>
On Tue, 17 Sep 2002 13:49:28 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> On Tue, Sep 17, 2002 at 10:43:42AM -0700, David Carlton wrote:
>> Is it okay to put up an RFA after I've switched over just blocks,
>> or do you want me to wait until after I've switched over global
>> symbols as well?
> Basically, at any point when you don't have a lot of temporary gunk.
Great; I'll get rid of all the DICT_TEMP gunk, finish converting
blocks over, and send out a new RFA. That won't take a separate
branch. And maybe before doing that I'll send out an RFA that gets
rid of BLOCK_SHOULD_SORT.
> How about a branch which require approval just like the mainline for
> large patches, although giving David a little more freedom to play
> around. Then, we'd allow large merges from the branch back to the
> trunk when they were ready and tested - larger patches than we'd
> normally accept all at once, because they'd already been approved.
From my point of view, having a separate branch could be quite useful
when getting to the global symbols, and what you propose could be a
reasonable mechanism. For one thing, it seems plausible to me that it
might take some amount of playing around with implementation methods
before settling on one that works well, so a branch is a natural place
for that sort of playing around to occur. And, for another thing,
having it be in a branch increases the chances that people other than
me can be shanghaied into working on this. (I can work on converting
appropriate code to using struct dictionaries, you can play around
with getting the interface to symbol lookups just right, and if we're
lucky Daniel Berlin can pop by every once in a while saying that he
took a break over the weekend from law school stuff to tear out all of
the psymtab->symtab translation and replace it with a new, improved
mechanism, or something like that.)
So I'm not resistant to branches generally.
Incidentally, I really should send out some e-mail that talks about
what I think the eventual interface to symbol lookups should be.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-09-17 18:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 15:26 David Carlton
2002-09-16 15:30 ` David Carlton
2002-09-17 7:35 ` Daniel Jacobowitz
2002-09-17 9:03 ` Andrew Cagney
2002-09-17 10:43 ` David Carlton
2002-09-17 10:49 ` Daniel Jacobowitz
2002-09-17 11:34 ` David Carlton [this message]
2002-09-17 12:24 ` Andrew Cagney
2002-09-17 11:44 ` Andrew Cagney
2002-09-17 12:30 ` Daniel Jacobowitz
2002-09-17 12:49 ` Andrew Cagney
2002-09-17 13:32 ` Daniel Jacobowitz
2002-09-17 21:48 ` Daniel Berlin
2002-09-18 7:26 ` Andrew Cagney
2002-09-20 9:13 ` Jim Blandy
2002-09-17 12:59 ` Daniel Berlin
2002-09-17 13:13 ` Andrew Cagney
2002-09-17 9:29 ` Andrew Cagney
2002-09-17 11:04 ` David Carlton
2002-09-17 12:16 ` Andrew Cagney
2002-09-17 12:35 ` Daniel Jacobowitz
2002-09-17 12:46 ` David Carlton
2002-09-17 12:57 ` Andrew Cagney
2002-09-22 14:51 ` Jim Blandy
2002-09-17 12:54 ` Michael Snyder
2002-09-17 12:59 ` Daniel Berlin
2002-09-18 2:56 ` Richard Earnshaw
2002-09-18 14:07 ` Andrew Cagney
2002-09-19 3:14 ` Richard Earnshaw
2002-09-19 6:18 ` Elena Zannoni
2002-09-19 7:52 ` Richard Earnshaw
2002-09-19 7:51 ` Andrew Cagney
2002-09-22 14:41 ` Jim Blandy
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=ro165x4fotl.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.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