Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: Not including the signatures in replies
Date: 17 Mar 1999 16:08:28 +0100	[thread overview]
Message-ID: <vafd8289ms3.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Didier Verna's message of "17 Mar 1999 15:18:59 +0100"

Didier Verna <verna@inf.enst.fr> writes:

  > [...] First, you cite the original in a somewhat raw manner (like
  > removing the signature) which I consider a job for gnus, and then,
  > you postprocess the citation to perform more clever stuff.

I think both Lars and Barry have said that this distinction should not
be made, i.e. removing the signature is a job for SC.

kai
-- 
I like _\bb_\bo_\bt_\bh kinds of music.


  reply	other threads:[~1999-03-17 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-17 13:19 Akim Demaille
1999-03-17 13:43 ` Norbert Koch
1999-03-17 13:53   ` Akim Demaille
1999-03-17 16:51     ` François Pinard
1999-03-17 13:58   ` Akim Demaille
1999-03-17 14:18     ` Didier Verna
1999-03-17 15:08       ` Kai.Grossjohann [this message]
1999-03-18 21:12     ` Christopher K Davis

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=vafd8289ms3.fsf@ramses.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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 NNTP newsgroup(s).