public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: "Daniel Berlin" <dberlin@dberlin.org>
Cc: overseers@sourceware.org
Subject: Re: disclaimer question
Date: Wed, 19 Sep 2007 14:09:00 -0000	[thread overview]
Message-ID: <m3zlzirbm3.fsf@gossamer.airs.com> (raw)
In-Reply-To: <4aca3dc20709190631ia292a85m91773e86007e1e83@mail.gmail.com>

"Daniel Berlin" <dberlin@dberlin.org> writes:

> Harmless.
> Doesn't attempt to bind the reader in any way, simply a statement of fact :)
> 
> On 9/19/07, Christopher Faylor
> <cgf-use-the-mailinglist-please@sourceware.org> wrote:
> > ----- Forwarded message -----
> >
> >      -  Disclaimer:  Statements made herein are not made on behalf of NIAID.
> >
> > ----- End forwarded message -----
> >
> > Should we be blocking the above or is it harmless?

I agree, this seems harmless.

Ian

      reply	other threads:[~2007-09-19 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 13:27 Christopher Faylor
2007-09-19 13:32 ` Daniel Berlin
2007-09-19 14:09   ` Ian Lance Taylor [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=m3zlzirbm3.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=dberlin@dberlin.org \
    --cc=overseers@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).