From: DJ Delorie <dj@redhat.com>
To: drow@mvista.com
Cc: keiths@redhat.com, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: [RFA] Makefile.tpl: Add maybe-configure-itcl to configure-gdb
Date: Wed, 18 Jun 2003 21:58:00 -0000 [thread overview]
Message-ID: <200306182156.h5ILue418417@greed.delorie.com> (raw)
In-Reply-To: <20030618212707.GA5602@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 18 Jun 2003 17:27:07 -0400)
> This is OK. It should be committed in gcc/ at the same time; if you
> don't have write access I guess DJ's sync scripts will pick it up?
My scripts notice that there's a difference, but they still have to be
manually applied.
next prev parent reply other threads:[~2003-06-18 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 21:24 Keith Seitz
2003-06-18 21:31 ` Daniel Jacobowitz
2003-06-18 21:35 ` Keith Seitz
2003-06-18 22:02 ` DJ Delorie
2003-06-18 21:58 ` DJ Delorie [this message]
2003-06-23 21:40 ` Keith Seitz
2003-06-25 4:05 ` [6.0 PATCH] " Keith Seitz
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=200306182156.h5ILue418417@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@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