public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "'cygwin-talk@cygwin.com'" <cygwin-talk@cygwin.com>
Subject: RE: Top post vs. bottom post (was: Re: [CFT] libtool on  	nix->cygwin cross,  with wine)
Date: Wed, 25 Feb 2009 13:14:00 -0000	[thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A29A674E45@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <20090225085624.GA27175@calimero.vinschen.de>

Corinna Vinschen wrote on Wednesday, February 25, 2009 3:56 AM:
> Which is exactly the reason why full quoting is not the way to go,
> either. 
> That's what bugs me all the time.  Why are people not willing or
> capable of removing all the stuff from a text which doesn't add
> anything to the discussion anymore?  

And the VERY worst is leaving in the footer (Unsubscribe, etc.).
The new post will just get another one.

      reply	other threads:[~2009-02-25 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <announce.49A35E97.5090808@cwilson.fastmail.fm>
     [not found] ` <49A37F05.8050900@cwilson.fastmail.fm>
     [not found]   ` <20090224123655.dd559d60.Rhubbell@iHubbell.com>
     [not found]     ` <49A46366.5050605@sbcglobal.net>
     [not found]       ` <20090224133507.543ed1cf.Rhubbell@iHubbell.com>
     [not found]         ` <87f94c370902241433h7701dae1lc652feb0abae8eae@mail.gmail.com>
     [not found]           ` <49A4786A.2060301@benjammin.net>
2009-02-25  8:24             ` Danilo Turina
2009-02-25  8:56               ` Corinna Vinschen
2009-02-25 13:14                 ` Buchbinder, Barry (NIH/NIAID) [E] [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=0105D5C1E0353146B1B222348B0411A29A674E45@NIHMLBX02.nih.gov \
    --to=bbuchbinder@niaid.nih.gov \
    --cc=cygwin-talk@cygwin.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).