Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [commit] Mark up add_com, add_info and add_prefix_cmd
Date: Thu, 17 Feb 2005 03:09:00 -0000	[thread overview]
Message-ID: <20050217003212.GA9895@nevyn.them.org> (raw)
In-Reply-To: <421246C4.8060003@gnu.org>

On Tue, Feb 15, 2005 at 02:00:20PM -0500, Andrew Cagney wrote:
> Daniel Jacobowitz wrote:
> >On Tue, Feb 15, 2005 at 10:48:14AM -0500, Andrew Cagney wrote:
> >
> >>FYI,
> >>committed,
> >>Andrew
> >
> >
> >Andrew, both Eli and I have asked you to stop doing committing these
> >patches.
> 
> (Which is funny.  When I indicated that I was stopping dw_op_piece 
> patches, you had the exact oposite reaction.  I guess you need 
> DW_OP_piece but not i18n)

What are you talking about?  I said that I still believed DW_OP_piece
was an important feature for GDB 6.4.  I haven't complained about your
struct value patches because there was nothing wrong with the patches
themselves.  (Although I have gotten testy with you for not explaining
what you are doing as you go along, as other contributors try to do.)

I don't think i18n is an important feature for GDB 6.4, because unlike
DW_OP_piece, we don't have an external "deadline" for it.  And marking
up the text in a hurry does eventual translation no favors.

> I'm doing my job as head developer: putting in the hard yards needed to 
> fix this tedious, long standing, and very long overdue problem in GDB - 
> getting bulk of the text marked up.
> 
> On the other hand, what I'm seeing from each of you is trivial 
> complaints and objections serving no purpose other than to block this task.

I second Eli's responses to these paragraphs.  I also second his
questions - all five of them.  And I'm within a hair of following his
last suggestion.

You've been increasingly rude to your fellow GDB developers for the
last few months.  Currently every active global maintainer outside
of Red Hat is annoyed at your behavior.  Doesn't that suggest anything
to you?

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      parent reply	other threads:[~2005-02-17  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 16:23 Andrew Cagney
2005-02-15 19:02 ` Daniel Jacobowitz
2005-02-15 21:17   ` Andrew Cagney
2005-02-15 23:35     ` Eli Zaretskii
2005-02-17  3:09     ` Daniel Jacobowitz [this message]

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=20050217003212.GA9895@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --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