From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] convert blocks to dictionaries, phase 1, main part
Date: Tue, 17 Sep 2002 10:49:00 -0000 [thread overview]
Message-ID: <20020917174928.GA23058@nevyn.them.org> (raw)
In-Reply-To: <ro1k7lkfr5d.fsf@jackfruit.Stanford.EDU>
On Tue, Sep 17, 2002 at 10:43:42AM -0700, David Carlton wrote:
> On Tue, 17 Sep 2002 10:35:53 -0400, Daniel Jacobowitz <drow@mvista.com> said:
>
> > I think that you should take Andrew's suggestion, though - create a
> > branch to finish this work on. It's a bit of a hassle, since you'll
> > need to do periodic merges to the branch, but I don't feel right
> > adding something with this many temporary interfaces and FIXMEs to
> > the trunk. Then you can commit patches on the branch without
> > approval, and get it into a stabler state.
>
> Sure, if that's what you want. 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?
>
> Obviously my attempt to make patches smaller by introducing temporary
> interfaces wasn't a smashing success. Ah well; I'll know better next
> time...
Basically, at any point when you don't have a lot of temporary gunk. I
confess, I'm of two minds about working on a branch for this sort of thing:
I consider it very impractical for things which don't break up into
pieces easily afterwards. GCC has been using an interesting approach,
which I think we could adapt and extend here.
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.
Andrew - thoughts? Does it have any interesting possibilities?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-09-17 17:49 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 [this message]
2002-09-17 11:34 ` David Carlton
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=20020917174928.GA23058@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@math.stanford.edu \
--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