Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: ac131313@redhat.com
Cc: klee@apple.com, neroden@doctormoo.dyndns.org,
	binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Update Darwin support in top-level configure.in
Date: Wed, 13 Nov 2002 10:27:00 -0000	[thread overview]
Message-ID: <200211131814.gADIE5U13558@envy.delorie.com> (raw)
In-Reply-To: <3DD28E8B.70803@redhat.com> (message from Andrew Cagney on Wed, 13 Nov 2002 12:40:27 -0500)


> I think this should be sent to GCC.  Nathanael is currently merging the 
> two top-level directories so the place to get this committed is in GCC.

Nathanael is doing the autoconfiscation.  The toplevel directories are
pretty much already merged, at least for the important bits we
maintain locally.  As far as I'm concerned, any top level patch can be
approved on either side, as long as it gets applied to both sides
(either by the submitter, or if they can't, by me).


      reply	other threads:[~2002-11-13 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13  9:13 Klee Dienes
2002-11-13  9:40 ` Andrew Cagney
2002-11-13 10:27   ` DJ Delorie [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=200211131814.gADIE5U13558@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=klee@apple.com \
    --cc=neroden@doctormoo.dyndns.org \
    /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