public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: 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: Tue, 10 Jun 2003 00:50:00 -0000	[thread overview]
Message-ID: <oru1ayahd4.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20030609163836.A20345@synopsys.com>

On Jun  9, 2003, Joe Buck <jbuck@synopsys.com> wrote:

> So first Christopher objects to a list having @codesourcery.com at the
> end, and now Alexandre wants @redhat.com at the end?

Heck, sorry.  It's just that, whenever I post a patch that affects the
toplevel, I have to cross-post it to half a dozen lists
@sources.redhat.com, and one @gcc.gnu.org.  I wouldn't mind having the
list @gcc.gnu.org, since gcc is allegedly the master copy.  I didn't
mean to push for @sources.redhat.com, I just meant to say I've always
wanted such a list.

> let's avoid any
> company conflicts by avoiding use of either company's domain as much as we
> can, OK?

You surely have a good point.  I don't, and I couldn't disagree with
it.  toplevel@gcc.gnu.org, deal?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

  parent reply	other threads:[~2003-06-10  0:50 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
2003-06-10  0:50         ` Alexandre Oliva [this message]
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=oru1ayahd4.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=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).