=================== BUG #3421: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3421&group_id=1968
Changes by: Earl Hood <earl(_at_)earlhood(_dot_)com>
Date: Fri 05/02/2003 at 12:10 (US/Central)
What | Removed | Added
---------------------------------------------------------------------------
Severity | 5 - Major | 1 - Ordinary
Bug Group | Incorrect Behavior | Undesired Behavior
Resolution | None | Invalid
Status | Open | Closed
Perl Version | ? | All
Component Version | ? | All
Fixed Release | | N/A
------------------ Additional Follow-up Comments ----------------------------
[Not a Bug]
This is completely unrelated to bug 372.
Technically, it is not a bug but an issue of how threading
is done by MHonArc. The key message to look at is:
http://lists.debian.org/debian-tetex-maint/2003/debian-tetex-maint-200304/msg00127.html
It is the data in the message header fields of this message
that is causing the "break" in the message. Take a look at
at the In-Reply-To field. It actually contains a reference
to message
<20030418(_dot_)084845(_dot_)74737713(_dot_)kohda(_at_)pm(_dot_)tokushima-u(_dot_)ac(_dot_)jp>
that
is in the thread about Bug 189341 in the debian list
(I've just noticed that savannah tries to auto-link bug
numbers in these messages, but in this case, these #'s
are not applicable to savannah).
MHonArc combines References and In-Reply-To, and it just
happens that In-Reply-To (IRT) is given higher precedence
in determining thread order vs References (see
read_mail_head() routine in mhamain.pl). Hence, the
question becomes, "Which actually has higher precedence?"
I do not think there is a clear-cut answer, and I
think any discussion about it should be moved to
mhonarc-dev.
This bug will be closed and any future discussion should
be done on the mhonarc-dev list since it is really a design
behavioral issue and not a bug.
=================== BUG #3421: FULL BUG SNAPSHOT ===================
Submitted by: jbuhl Project: MHonArc
Submitted on: Fri 05/02/2003 at 05:01
Category: Threading Severity: 1 - Ordinary
Bug Group: Undesired Behavior Resolution: Invalid
Assigned to: None Status: Closed
Platform Version: All Perl Version: All
Component Version: All Fixed Release: N/A
Summary: Mails not sorted into correct thread
Original Submission: Description by example:
In the Debian Mail Archive for debian-tetex-maint for April 2003, Messages in
the thread "#Bug#190721: splitting of texdoctk is hosed" suddenly started
getting displayed in thread "Bug#189341: tetex-bin: texdoctk not packaged
correctly" although the subject is certainly unambiguous.
Here's a link to the archive:
http://lists.debian.org/debian-tetex-maint/2003/debian-tetex-maint-200304/threads.html
I guess this could be bug #372, but I have no idea. sorry if it's a duplicate
of that bug.
Follow-up Comments
*******************
-------------------------------------------------------
Date: Fri 05/02/2003 at 12:10 By: ehood
[Not a Bug]
This is completely unrelated to bug 372.
Technically, it is not a bug but an issue of how threading
is done by MHonArc. The key message to look at is:
http://lists.debian.org/debian-tetex-maint/2003/debian-tetex-maint-200304/msg00127.html
It is the data in the message header fields of this message
that is causing the "break" in the message. Take a look at
at the In-Reply-To field. It actually contains a reference
to message
<20030418(_dot_)084845(_dot_)74737713(_dot_)kohda(_at_)pm(_dot_)tokushima-u(_dot_)ac(_dot_)jp>
that
is in the thread about Bug 189341 in the debian list
(I've just noticed that savannah tries to auto-link bug
numbers in these messages, but in this case, these #'s
are not applicable to savannah).
MHonArc combines References and In-Reply-To, and it just
happens that In-Reply-To (IRT) is given higher precedence
in determining thread order vs References (see
read_mail_head() routine in mhamain.pl). Hence, the
question becomes, "Which actually has higher precedence?"
I do not think there is a clear-cut answer, and I
think any discussion about it should be moved to
mhonarc-dev.
This bug will be closed and any future discussion should
be done on the mhonarc-dev list since it is really a design
behavioral issue and not a bug.
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3421&group_id=1968
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-DEV
