From: Daniel Jacobowitz <drow@mvista.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: Alexandre Oliva <aoliva@redhat.com>,
Christopher Faylor <cgf@redhat.com>,
gcc@gcc.gnu.org, binutils@sources.redhat.com,
gdb@sources.redhat.com
Subject: Re: Updating to Autoconf 2.5x
Date: Mon, 09 Jun 2003 23:58:00 -0000 [thread overview]
Message-ID: <20030609234355.GA21222@nevyn.them.org> (raw)
In-Reply-To: <20030609163836.A20345@synopsys.com>
On Mon, Jun 09, 2003 at 04:38:36PM -0700, Joe Buck wrote:
>
> On Jun 9, 2003, Christopher Faylor <cgf@redhat.com> wrote:
> > > I agree. It's sort of odd to have important gcc issues like this talked
> > > about somewhere outside of the gcc.gnu.org domain.
>
> On Mon, Jun 09, 2003 at 07:58:30PM -0300, Alexandre Oliva wrote:
> > I've always wanted us to have toplevel@ or
> > configure@sources.redhat.com, for all projects hosted in s.r.c., and
> > GCC too, just because GCC shares most of the top-level files with
> > that. Can't we go ahead and create one of these lists, in which we'll
> > discuss not only this transition, but also any patches that affect the
> > top level alone?
>
> So first Christopher objects to a list having @codesourcery.com at the
> end, and now Alexandre wants @redhat.com at the end? Thanks to both
> companies for giving us so much free software work, but let's avoid any
> company conflicts by avoiding use of either company's domain as much as we
> can, OK? To do otherwise will just confuse people into thinking that
> something is a single-company effort, when it is not.
Joe, please bear in mind that all the non-GCC projects affected by this
- there are quite a lot of them - are already hosted at
sources.redhat.com and have their mailing lists there.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-09 23:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 20:32 Zack Weinberg
2003-06-09 21:05 ` Andrew Cagney
2003-06-09 21:09 ` Christopher Faylor
2003-06-09 22:58 ` Alexandre Oliva
2003-06-09 23:06 ` Daniel Jacobowitz
2003-06-09 23:38 ` Joe Buck
2003-06-09 23:48 ` DJ Delorie
2003-06-10 0:33 ` Joe Buck
2003-06-10 4:40 ` Zack Weinberg
2003-06-10 6:42 ` Mark Mitchell
2003-06-10 9:25 ` Joseph S. Myers
2003-06-10 14:24 ` Christopher Faylor
2003-06-10 15:57 ` Mark Mitchell
2003-06-10 16:40 ` Christopher Faylor
2003-06-12 4:16 ` Red Hat logos on FSF web pages (was Re: Updating to Autoconf 2.5x) Christopher Faylor
2003-06-10 17:40 ` Updating to Autoconf 2.5x Andrew Cagney
2003-06-10 13:48 ` Kaveh R. Ghazi
2003-06-10 14:23 ` Christopher Faylor
2003-06-10 14:30 ` Daniel Jacobowitz
2003-06-10 15:44 ` Andrew Cagney
2003-06-10 16:03 ` Mark Mitchell
2003-06-10 17:47 ` Joe Buck
2003-06-09 23:58 ` Daniel Jacobowitz [this message]
2003-06-10 0:50 ` Alexandre Oliva
2003-06-10 0:55 ` DJ Delorie
2003-06-10 2:58 ` Christopher Faylor
2003-06-10 3:43 ` Ian Lance Taylor
2003-06-10 2:37 ` Christopher Faylor, Christopher Faylor
2003-06-09 21:15 ` DJ Delorie
2003-06-09 23:01 ` Zack Weinberg
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=20030609234355.GA21222@nevyn.them.org \
--to=drow@mvista.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cgf@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jbuck@synopsys.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).