public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org, insight@sourceware.org
Subject: Re: [RFC] change sources.redhat.com to sourceware.org in 	gdbadmin/ss dir (was:  libiberty configuration for DJGPP)
Date: Tue, 14 Apr 2009 19:21:00 -0000	[thread overview]
Message-ID: <20090414192117.GA21240@ednor.casa.cgf.cx> (raw)
In-Reply-To: <006801c9bd1d$aa40bb40$fec231c0$@u-strasbg.fr>

On Tue, Apr 14, 2009 at 06:25:46PM +0200, Pierre Muller wrote:
>I proposed this patch for gdbadmin/ss directory
>
>Ian tought it was a good idea, and added that I should ask 
>directly on insight mailing list about this issue I raised:
>
>I am not really sure about insight reference in README,
>as this is still seems to be more a redhat
>than a GNU project.
>
>Should we leave sources.redhat.com for all insight related references
>or also switch to sourceware.org?

The name of the site really is sourceware.org but insight isn't really
officially supported by Red Hat anymore (and hasn't been for years) so I
don't see any reason to keep the .redhat.com for insight's sake.

If we were talking about something like systemtap or frysk then that
would be a different story...

cgf

      parent reply	other threads:[~2009-04-14 19:21 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       ` Pierre Muller
2009-04-14 17:12         ` [RFC] change sources.redhat.com to sourceware.org in gdbadmin/ss dir Keith Seitz
2009-04-14 19:21         ` Christopher Faylor [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=20090414192117.GA21240@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=insight@sourceware.org \
    /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).