From: Keith Seitz <keiths@redhat.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: insight@sourceware.org
Subject: Re: [RFC] change sources.redhat.com to sourceware.org in gdbadmin/ss dir
Date: Tue, 14 Apr 2009 17:12:00 -0000 [thread overview]
Message-ID: <49E4C3E7.4000308@redhat.com> (raw)
In-Reply-To: <006801c9bd1d$aa40bb40$fec231c0$@u-strasbg.fr>
Pierre Muller wrote:
> Should we leave sources.redhat.com for all insight
> related references or also switch to sourceware.org?
While it *appears* that Insight is still only a Red Hat project, it was
never certainly meant to be. I won't go into the history, but let's just
say that the biggest reason this appears true is because insight is
basically maintained by one person who happens to work for Red Hat (but
it is not his job).
Please make the proposed changes to sourceware.org. I don't mind.
Keith
next prev parent reply other threads:[~2009-04-14 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83zlejmkgb.fsf@gnu.org>
[not found] ` <m3eivv5n8e.fsf@google.com>
[not found] ` <83skkbmhk6.fsf@gnu.org>
[not found] ` <m3ocuz474n.fsf@google.com>
2009-04-14 16:25 ` [RFC] change sources.redhat.com to sourceware.org in gdbadmin/ss dir (was: libiberty configuration for DJGPP) Pierre Muller
2009-04-14 17:12 ` Keith Seitz [this message]
2009-04-14 19:21 ` Christopher Faylor
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=49E4C3E7.4000308@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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).