public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Mike Stump <mrs@apple.com>
Cc: overseers@sources.redhat.com
Subject: Re: Fwd: Target processor detection
Date: Fri, 18 Nov 2005 18:51:00 -0000	[thread overview]
Message-ID: <m3psoxygur.fsf@gossamer.airs.com> (raw)
In-Reply-To: <6904F90B-D77C-4A08-984C-F5D5A5DC597F@apple.com>

Mike Stump <mrs@apple.com> writes:

> Do we have any policy on very long and annoying signatures?  Should we?

We don't have a policy on long and annoying signatures, but we do have
a policy on signatures like this one which prohibit disseminating the
information.  They are prohibited, as described on
    http://gcc.gnu.org/lists.html

When I feel like it, I reply suggesting the use of a free e-mail web
based e-mail account instead.

There has been some discussion of detecting these and blocking them
automatically, but it has not been implemented.

Ian

  reply	other threads:[~2005-11-18 18:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <009f01c5ec3a$ee023eb0$df0a0a0a@piotrw>
2005-11-18 18:06 ` Mike Stump
2005-11-18 18:51   ` Ian Lance Taylor [this message]
2005-11-18 20:28     ` Matthew Galgoci
2005-11-19  4:32     ` 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=m3psoxygur.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=mrs@apple.com \
    --cc=overseers@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).