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 06:31:00 -0000	[thread overview]
Message-ID: <uoermbbdr.fsf@elta.co.il> (raw)
In-Reply-To: <D898B023-6821-11D8-B051-000A95DA505C@dberlin.org> (message from Daniel Berlin on Thu, 26 Feb 2004 01:05:58 -0500)

> From: Daniel Berlin <dberlin@dberlin.org>
> Date: Thu, 26 Feb 2004 01:05:58 -0500
> 
> Andrew continually claimed provably untrue things that could do nothing 
> but piss off people involved in the hard work that went on in the gcc 
> tree-ssa branch (schedule slippage, too many resources consumed, etc)

I think you are exaggerating.  Andrew expressed concerns about
technical issues based on whatever information he had.  I don't know
whom he was talking to, and I'm ignorant of the subject matter because
I don't track GCC lists, but my outsider's judgement is that his
argument was of a technical nature, and I don't see why someone would
spot any sign of malice in what he wrote.  He might be mistaken, as we
all are sometimes, but his is a genuine concern, not a wish to piss
off.

> This is generally known as trolling.

I think you know Andrew all too well to suspect that he is trollying.

> I'm seriously concerned that if he thinks the tree-ssa branch is 
> somehow an example of a bad development plan, that gdb development is 
> going down the wrong path.

I understand his comments differently: that he fears that merging
large branches _could_ have adverse side effects if things get out of
control.  In other words, it was a general comment on large merges,
not something too specific about the specific case of tree-ssa.

> I'm also seriously concerned that if he somehow thinks DW_OP_piece 
> support is more important than the intercu-branch, that he is also 
> going down the wrong path.

It's not more important in general, but since we are preparing to cut
the 6.1 branch in a few days, DW_OP_piece might be a good thing to do
now, while delaying intercu-branch merge till after the release.
It's a question of timing, not of an abstract importance.


  reply	other threads:[~2004-02-26  6:31 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 [this message]
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
  -- 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=uoermbbdr.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