From: Fernando Nasser <fnasser@cygnus.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Fernando Nasser <fnasser@redhat.com>,
Ian Roxborough <irox@evilpeople.com>,
insight@sources.redhat.com, gdb@sources.redhat.com,
Michael Snyder <msnyder@cygnus.com>,
Eli Zaretskii <eliz@is.elta.co.il>,
Elena Zannoni <ezannoni@cygnus.com>, Jim Blandy <jimb@cygnus.com>,
Chris Faylor <cgf@cygnus.com>, Kevin Buettner <kevinb@cygnus.com>
Subject: Re: [PATCH] prep for Tcl/Tk 8.3 upgrade
Date: Wed, 16 May 2001 15:55:00 -0000 [thread overview]
Message-ID: <3B030520.DF1844CE@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0105160710110.25128-100000@ryobi.cygnus.com>
Keith Seitz wrote:
>
> On Wed, 16 May 2001, Andrew Cagney wrote:
>
> > There was a proposal to create an Insight maintainers file co-ordinated
> > by the Insight maintainers. Right now things are a little wierd. I'm
> > not responsible for Insight but that isn't clear since Insight is listed
> > in the GDB MAINTAINERS file.
>
> Yes, I was working on this at one time (and forgot all about it). If it is
> agreeable to everyone else, I will remove most of the Insight/gdbtk
> references in gdb/MAINTAINERS and move them to gdb/gdbtk/MAINTAINERS.
>
> The idea was to largely keep the same policies. Everyone with write
> authority in gdb would automatically have write-after-approval in gdbtk.
>
> Let me know.
> Keith
I agree.
--
Fernando Nasser
Red Hat Canada Ltd.
prev parent reply other threads:[~2001-05-16 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010514170524.164d5bf3.irox@evilpeople.com>
2001-05-15 12:25 ` Fernando Nasser
2001-05-16 6:08 ` Andrew Cagney
2001-05-16 7:14 ` Keith Seitz
2001-05-16 15:55 ` Fernando Nasser [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=3B030520.DF1844CE@cygnus.com \
--to=fnasser@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=cgf@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=ezannoni@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=irox@evilpeople.com \
--cc=jimb@cygnus.com \
--cc=keiths@cygnus.com \
--cc=kevinb@cygnus.com \
--cc=msnyder@cygnus.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