Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB's roles
Date: Fri, 21 Feb 2003 20:44:00 -0000	[thread overview]
Message-ID: <3E5690BB.5060104@redhat.com> (raw)
In-Reply-To: <20030221185123.GA18445@nevyn.them.org>

> 
> One of my concerns from my previous thread about this, which seems to
> have died, ...

`shit happens'.

If you check your mailbox you'll notice an e-mail I sent in november to 
the global maintainers that identified a number of problem areas (from 
memory, I delayed sending it until you'd been made a global maintainer). 
  You'll note that Java was top of that list and I've since managed to 
resolve it -  Java patches have just started to flow again.  Your 
discussion has helped clarify a few things and re-prioritize accordingly.

As the `adminstrator', I get to follow through all of this.

Andrew



      parent reply	other threads:[~2003-02-21 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21 18:43 Andrew Cagney
2003-02-21 18:51 ` Daniel Jacobowitz
2003-02-21 20:21   ` Andrew Cagney
2003-02-21 20:44   ` Andrew Cagney [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=3E5690BB.5060104@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@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