From: Reiner Steib <reinersteib+gmane@imap.cc>
To: <ding@gnus.org>
Cc: bugs@gnus.org, jidanni@jidanni.org
Subject: Re: "duplicate" warning misleading
Date: Mon, 12 Nov 2007 10:58:15 +0100 [thread overview]
Message-ID: <v9lk93945k.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87y7d4asdl.fsf@jidanni.org> (jidanni@jidanni.org's message of "Mon, 12 Nov 2007 14:29:42 +0800")
On Mon, Nov 12 2007, jidanni@jidanni.org wrote:
> Saying
> Gnus-Warning: This is a duplicate of message <123zzz@eee.fff>
> is misleading. Say instead
> Gnus-Warning: Same ID <123zzz@eee.fff>, as other message(s)
I don't want to change the wording because this would break the split
methods of many users. Cf. (info "(gnus)Duplicates").
We could add a warning about such problems in the manual, though.
> As the user added an attachment, and resent it to me
> -rw-r--r-- 1 jidanni 50765 2007-11-12 14:22 fof
> -rw-r--r-- 1 jidanni 97144 2007-11-12 14:22 fof2
> and his mailer didn't change the ID.
Which mailer behaves like this?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2007-11-12 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y7d4asdl.fsf@jidanni.org>
2007-11-12 9:58 ` Reiner Steib [this message]
2007-11-12 19:59 ` jidanni
2007-11-12 21:21 ` Reiner Steib
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=v9lk93945k.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.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).