Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
	gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
	binutils@sources.redhat.com, dj@redhat.com
Subject: Re: Toplevel Makefile.tpl cleanup 1/n
Date: Tue, 25 Feb 2003 23:07:00 -0000	[thread overview]
Message-ID: <20030225230715.GA29548@daikokuya.co.uk> (raw)
In-Reply-To: <87wujox9wo.fsf@egil.codesourcery.com>

Zack Weinberg wrote:-

> At this point I suspect you know more about the top level build
> structure than most of us.  Perhaps you should be made official
> maintainer of that, not needing to seek these approvals?

FWIW I agree.  Nathanael's shown he's more than competent in this area
over quite some time now.

Neil.


  reply	other threads:[~2003-02-25 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 20:37 Nathanael Nerode
2003-02-25 22:39 ` Zack Weinberg
2003-02-25 23:07   ` Neil Booth [this message]
2003-02-27 20:34 ` DJ Delorie
2003-02-25 22:55 Nathanael Nerode

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=20030225230715.GA29548@daikokuya.co.uk \
    --to=neil@daikokuya.co.uk \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=neroden@twcny.rr.com \
    --cc=zack@codesourcery.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