Summary | Add "In-Reply-To" header |
Queue | Whups |
Queue Version | HEAD |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | jan (at) horde (dot) org |
Requester | selsky (at) columbia (dot) edu |
Created | 07/23/2008 (6295 days ago) |
Due | |
Updated | 08/25/2008 (6262 days ago) |
Assigned | |
Resolved | 08/25/2008 (6262 days ago) |
Milestone | |
Patch | No |
http://cvs.horde.org/diff.php/whups/docs/CHANGES?r1=1.201&r2=1.202&ty=u
http://cvs.horde.org/diff.php/whups/lib/Driver.php?r1=1.197&r2=1.198&ty=u
http://cvs.horde.org/diff.php/whups/lib/Ticket.php?r1=1.99&r2=1.100&ty=u
State ⇒ Accepted
$threadingmarker = "In-Reply-To: <bug-$id-" . $user->id . "$sitespec>"
We could the following:
"In-Reply-To: <bug-$id-" . md5($mail) . "$sitespec>"
State ⇒ Rejected
In-Reply-To: <bug-3617-62@https.bugzilla.example.com/>
References: <bug-3617-62@https.bugzilla.example.com/>
State ⇒ Feedback
message ids from notification messages with the comments that
triggered the notification, this might even render impossible, because
we send individual messages now to each user, so that we don't have a
single message id anymore.
State ⇒ New
Patch ⇒ No
Milestone ⇒
Queue ⇒ Whups
Summary ⇒ Add "In-Reply-To" header
Type ⇒ Enhancement
Priority ⇒ 1. Low