public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gcc@gcc.gnu.org, binutils@gcc.gnu.org, gdb@sources.redhat.com
Subject: Red Hat logos on FSF web pages (was Re: Updating to Autoconf 2.5x)
Date: Thu, 12 Jun 2003 04:16:00 -0000	[thread overview]
Message-ID: <20030612041635.GA9714@redhat.com> (raw)
In-Reply-To: <20030610164031.GA19400@redhat.com>

On Tue, Jun 10, 2003 at 12:40:31PM -0400, Christopher Faylor wrote:
>On Tue, Jun 10, 2003 at 08:56:51AM -0700, Mark Mitchell wrote:
>>That's all well and good, but the basic point certainly remains: we've
>>worked very hard to make GCC appear to come entirely from a machine
>>named gcc.gnu.org, and similar work has not been done for GDB, binutils,
>>glibc, etc.  Red Hat domain names and logos appear frequently on those
>>web pages.
>
>If anyone has specific examples, I'll see about getting this changed.  I
>didn't see anything at a quick glance.  I know that the cvs instructions
>(obviously?) specify sources.redhat.com but I don't know why there
>should be Red Hat logos on FSF projects.  That's just wrong.  FWIW, I
>removed some of the more flashy logos from some of the
>sources.redhat.com web pages a while ago.

Hello?  Anyone with examples?

I would rather not leave these insinuations hanging since, IMO, it
reflects badly on my company and I want to get any improprieties fixed.
Putting Red hat logos on any FSF web page is clearly wrong and putting
any redhat.com addresses other than sources.redhat.com on the web pages
is pretty iffy, too.  I just took another look at some project web pages
and didn't see any evidence of this behavior so I need help to get
to the bottom of this allegation.

Or is this maybe another urbane myth like "gdb never builds", oft-repeated
and wildly inaccurate?

cgf

  reply	other threads:[~2003-06-12  4:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 20:32 Updating to Autoconf 2.5x 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                       ` Christopher Faylor [this message]
2003-06-10 17:40                     ` 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
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=20030612041635.GA9714@redhat.com \
    --to=cgf@redhat.com \
    --cc=binutils@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).