From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnimap article editing
Date: Thu, 09 Oct 2008 14:04:35 -0500 [thread overview]
Message-ID: <86od1tr3ng.fsf@lifelogs.com> (raw)
In-Reply-To: <8763o1d620.fsf@marauder.physik.uni-ulm.de>
On Thu, 09 Oct 2008 19:36:23 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> On Thu, Oct 09 2008, Ted Zlatanov wrote:
>> The new one should have the same Message-ID but otherwise
>> can be completely different. It doesn't even need the same Message-ID,
>> it can be treated as a followup if that breaks any functionality.
RS> Creating a new Message-ID would break threading. The edited article
RS> should have the same Message-ID, as we do for nnml, etc.
Do you know of anything that would break if two messages have the same
Message-ID? I don't, so I agree with you that we should stick with the
same Message-ID, but my point was that if there is such functionality
that depends on unique Message-IDs we will have to fix it or change the
Message-ID of the new message.
Ted
next prev parent reply other threads:[~2008-10-09 19:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 10:20 Didier Verna
2008-10-09 11:52 ` David Engster
2008-10-09 13:44 ` Ted Zlatanov
2008-10-09 14:58 ` David Engster
2008-10-09 17:21 ` Ted Zlatanov
2008-10-09 17:36 ` Reiner Steib
2008-10-09 19:04 ` Ted Zlatanov [this message]
2008-10-09 20:02 ` Christoph Conrad
2008-10-09 20:25 ` Ted Zlatanov
2008-10-09 21:23 ` Christoph Conrad
2008-10-09 20:45 ` Reiner Steib
2008-10-10 13:07 ` Ted Zlatanov
2008-10-10 18:14 ` Reiner Steib
2008-10-13 13:21 ` Ted Zlatanov
2008-11-03 15:25 ` Gnus CVS checkins (was: nnimap article editing) Ted Zlatanov
2008-11-03 20:19 ` Gnus CVS checkins Reiner Steib
2008-11-03 20:46 ` Ted Zlatanov
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=86od1tr3ng.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).