Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: "gmane dicuss" <gmane-discuss@hawk.netfonds.no>
Subject: Re: gnus/spam-report.el: User-Agent for Gmane spam reporting
Date: 20 Sep 2005 12:39:07 -0400	[thread overview]
Message-ID: <4naci7k82c.fsf@lifelogs.com> (raw)
In-Reply-To: <v9irx16w4i.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 16 Sep 2005 14:21:49 +0200")

On Fri, 16 Sep 2005, reinersteib+gmane@imap.cc wrote:

> wouldn't it be nice to use `gnus-extended-version' instead of
> `gnus-emacs-version' for the Gmane spam reporting?  This would include
> Gnus version which is more useful in this context, IMO.
> 
> ELISP> (gnus-emacs-version)
> "Emacs/22.0.50 (gnu/linux)"
> ELISP> (gnus-extended-version)
> "Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)"
> 
> Unless Gmane prefers the current format for some reason, I'll commit
> this change:

Works for me.  Thanks!
Ted

      reply	other threads:[~2005-09-20 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 12:21 Reiner Steib
2005-09-20 16:39 ` Ted Zlatanov [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=4naci7k82c.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=gmane-discuss@hawk.netfonds.no \
    /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).