From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: [PATCH] private message id
Date: Wed, 01 Dec 2010 18:09:28 +0100 [thread overview]
Message-ID: <m3pqtlifnb.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87r5e22t87.fsf%lukasz.stelmach@iem.pw.edu.pl>
Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:
> This is an option. However, there is the whole superseding code which
> looks like it should be there. So copying a function just to redefine
> two lines in it looks weird, doesn't it?
It's really the message-unique-id and/or message-make-fqdn that need
redefinition, isn't it?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-01 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 21:37 Łukasz Stelmach
2010-11-29 21:41 ` Russ Allbery
2010-11-30 20:35 ` Lars Magne Ingebrigtsen
2010-12-01 1:10 ` Łukasz Stelmach
2010-12-01 17:09 ` Lars Magne Ingebrigtsen [this message]
2010-12-01 23:16 ` Łukasz Stelmach
2010-12-05 12:30 ` Lars Magne Ingebrigtsen
2010-12-06 6:28 ` Łukasz Stelmach
2010-12-06 19:40 ` Lars Magne Ingebrigtsen
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=m3pqtlifnb.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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).