From: "Sebastian P. Luque" <spluque@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: message-signature-file toggled to nil locally
Date: Sun, 03 Feb 2008 17:10:29 -0600 [thread overview]
Message-ID: <87lk61tz4q.fsf@patagonia.sebmags.homelinux.org> (raw)
In-Reply-To: <v9lk613m92.fsf@marauder.physik.uni-ulm.de>
On Sun, 03 Feb 2008 19:53:13 +0100,
Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> I see. Does the following quite untested patch do the right thing?
Thanks Reiner for this patch! I'm getting a double signature with it
though. It's probably not taking into account that some signature has
been inserted through gnus-posting-styles.
next prev parent reply other threads:[~2008-02-03 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 16:38 Sebastian P. Luque
2008-02-03 17:12 ` Reiner Steib
2008-02-03 17:59 ` Sebastian P. Luque
2008-02-03 18:53 ` Reiner Steib
2008-02-03 23:10 ` Sebastian P. Luque [this message]
2008-02-03 22:18 ` Sebastian P. Luque
[not found] ` <mailman.6907.1202077097.18990.info-gnus-english@gnu.org>
2008-02-04 10:42 ` Slackrat
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=87lk61tz4q.fsf@patagonia.sebmags.homelinux.org \
--to=spluque@gmail.com \
--cc=info-gnus-english@gnu.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 NNTP newsgroup(s).