Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: cagney@gnu.org, drow@false.org,gdb@sources.redhat.com,
	mec.gnu@mindspring.com
Subject: Re: Branch created for inter-compilation-unit references
Date: Thu, 26 Feb 2004 05:48:00 -0000	[thread overview]
Message-ID: <uu11ebdbs.fsf@elta.co.il> (raw)
In-Reply-To: <1037DDEA-67B5-11D8-9146-000A95DA505C@dberlin.org> (message from Daniel Berlin on Wed, 25 Feb 2004 12:07:16 -0500)

> From: Daniel Berlin <dberlin@dberlin.org>
> Date: Wed, 25 Feb 2004 12:07:16 -0500
> 
> >
> > A comparison is reasonable (and it isn't ment to degrate SSA or GCC). 
> > If the HP merge were to have been handled correctly it would have 
> > turned into a project of size and logistics comparable to SSA.  That, 
> > I think, is getting out of control.
> 
> Then you are sorely mistaken.
> If you think the SSA branch is an example of a  bad thing, i fear for 
> gdb development.

Don't fear.

I think you are reading too much into Andrew's comments, and therefore
miss his point.  As I understand what Andrew says, he simply is afraid
that merging large modifications brings a danger of repeating past
mistakes such as the HP merge.  I think the point is valid, and we
should be aware of that danger so that the problems don't repeat.


  parent reply	other threads:[~2004-02-26  5:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  3:51 Michael Elizabeth Chastain
2004-02-25  5:12 ` Andrew Cagney
2004-02-25 16:10   ` Daniel Berlin
2004-02-25 17:01     ` Andrew Cagney
2004-02-25 17:07       ` Daniel Berlin
2004-02-25 18:50         ` Andrew Cagney
2004-02-25 18:53           ` Daniel Berlin
2004-02-25 19:48             ` Andrew Cagney
2004-02-26  5:48             ` Eli Zaretskii
2004-02-26  6:06               ` Daniel Berlin
2004-02-26  6:31                 ` Eli Zaretskii
2004-02-26 15:05                   ` Daniel Jacobowitz
2004-02-26 16:19                     ` Elena Zannoni
2004-02-26 16:25                       ` Daniel Jacobowitz
2004-02-26 16:36                         ` Elena Zannoni
2004-02-26 16:54                           ` Daniel Jacobowitz
2004-02-26 19:01                           ` Eli Zaretskii
2004-02-26 19:10                     ` Eli Zaretskii
2004-02-26 19:24                     ` Andrew Cagney
2004-02-26 19:28                       ` Daniel Jacobowitz
2004-02-26 20:19                         ` Andrew Cagney
2004-02-26  5:48         ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-21 20:08 Daniel Jacobowitz
2004-02-25  0:18 ` Daniel Jacobowitz
2004-02-25  0:35   ` Andrew Cagney
2004-02-25  1:29     ` Daniel Jacobowitz
2004-02-25  2:23       ` Andrew Cagney
2004-02-25  2:27         ` Daniel Jacobowitz
2004-02-25  3:17           ` Andrew Cagney

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=uu11ebdbs.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=cagney@gnu.org \
    --cc=dberlin@dberlin.org \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.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