From: Jesper Harder <harder@myrealbox.com>
Subject: Re: message-unique-id
Date: Wed, 16 Apr 2003 01:19:23 +0200 [thread overview]
Message-ID: <m3r8835oxw.fsf@defun.localdomain> (raw)
In-Reply-To: <hhhe90g6ey.fsf@hrothgar.la.mastaler.com>
"Jason R. Mastaler" <jason@mastaler.com> writes:
> The end of `message-unique-id' says:
>
> ;; Append the newsreader name, because while the generated
> ;; ID is unique to this newsreader, other newsreaders might
> ;; otherwise generate the same ID via another algorithm.
> ".fsf")))
>
> Last time I checked, ``fsf'' wasn't the name of this newsreader. I
> suggest changing this string to ".gnus" to reduce the chance of
> collision with other softwares.
I think the 'message' library is intended to be usable by other clients
than Gnus. The string "fsf" makes more sense than "gnus" in that light,
IMHO.
prev parent reply other threads:[~2003-04-15 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 20:39 message-unique-id Jason R. Mastaler
2003-04-15 22:35 ` message-unique-id Lars Magne Ingebrigtsen
2003-04-15 22:56 ` message-unique-id Jason R. Mastaler
2003-04-15 23:17 ` message-unique-id Lars Magne Ingebrigtsen
2003-04-15 23:08 ` message-unique-id Paul Jarc
2003-04-15 23:19 ` message-unique-id Lars Magne Ingebrigtsen
2003-04-15 23:19 ` Jesper Harder [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=m3r8835oxw.fsf@defun.localdomain \
--to=harder@myrealbox.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 NNTP newsgroup(s).