From: Ben Elliston <bje+dated+1120598214.a7b07a@air.net.au>
To: DJ Delorie <dj@redhat.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
gcc-patches@gcc.gnu.org
Subject: Re: some top-level changes
Date: Thu, 30 Jun 2005 21:17:00 -0000 [thread overview]
Message-ID: <20050701071650.B11816@mailhub.air.net.au> (raw)
In-Reply-To: <200506302049.j5UKnXmC012925@greed.delorie.com>; from dj@redhat.com on Thu, Jun 30, 2005 at 04:49:33PM -0400
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
> We have a number of other projects listed there that aren't part of
> our source trees (like "hello" or "textutils"). Why can't expect
> and dejagnu have the same status? Is there any harm in leaving them
> in? You never know when some third party (Red Hat Inc comes to
> mind) will want to build everything in one tree themselves.
This is the objection I was anticipating and, if that's considered to
be the case, then that's fine. Patch withdrawn. :-)
Ben
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-06-30 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 7:08 Ben Elliston
2005-06-30 20:51 ` DJ Delorie
2005-06-30 21:17 ` Ben Elliston [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=20050701071650.B11816@mailhub.air.net.au \
--to=bje+dated+1120598214.a7b07a@air.net.au \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@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