From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Johann 'Myrkraverk' Oskarsson" <myrkraverk@gmx.com>
Cc: Gnus Ding <ding@gnus.org>
Subject: Re: Time to revisit the message id generation algorithm?
Date: Mon, 06 Feb 2012 23:12:37 +0100 [thread overview]
Message-ID: <87d39rk3vu.fsf@gnus.org> (raw)
In-Reply-To: <yky1gk.x5yky1gk.mx91.5dlc.gnus@asuka.myrkraverk.com> (Johann Oskarsson's message of "Thu, 02 Feb 2012 17:50:39 +0000")
"Johann 'Myrkraverk' Oskarsson" <myrkraverk@gmx.com> writes:
> I'm likely to come up with some proposals in the near future. For
> example, I might bring a patch for the following configuration
> variables: message-unique-id-use-uid, message-unique-id-prefix,
> message-unique-id-suffix. Where the defaults are t, "" and ".fsf"
> respectively.
This seems like overengineering. If you want a different Message-ID,
just redefine the `message-make-message-id' function.
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
prev parent reply other threads:[~2012-02-06 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vbaknx.x5vbaknx.vcnr.u432.gnus@asuka.myrkraverk.com>
[not found] ` <87sjit4k1b.fsf@gnus.org>
2012-02-02 17:50 ` Johann 'Myrkraverk' Oskarsson
2012-02-06 22:12 ` Lars Ingebrigtsen [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=87d39rk3vu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=myrkraverk@gmx.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).