[LLVMbugs] [Bug 23880] New: Phabricator sometimes likes to send duplicate messages
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Wed Jun 17 16:50:54 PDT 2015
https://llvm.org/bugs/show_bug.cgi?id=23880
Bug ID: 23880
Summary: Phabricator sometimes likes to send duplicate messages
Product: Website
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Phabricator
Assignee: unassignedbugs at nondot.org
Reporter: llvm-bugs at justinbogner.com
CC: klimek at google.com, llvmbugs at cs.uiuc.edu
Classification: Unclassified
Every so often two almost identical mails show up on a phabricator thread. It
looked to me like this happens when somebody top-posts in an email reply to a
phabricator thread - one mail goes to the list from the email author, another
from phab. If this is what's happening, we should teach phab not to send the
mail if the destination is already in the recipients list.
When I was looking at an example of this happening though, it looks like it
might be more complicated than that. Consider these two mails:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150615/281960.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150615/281961.html
They're identical, except the former is missing the part with inline replies.
You'd think my explanation above was correct: the latter was from Chandler to
the list, and the former from phab. This theory gets a bit muddier though,
because both of these emails have the following headers:
X-Phabricator-Sent-This-Message: Yes
X-Phabricator-Mail-Tags: <differential-comment>
So I guess *both* came from phabricator? That's weird.
In any case, I'd really like to only receive the version with the full content,
and not the one that repeats the start of the content.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20150617/c6fe9e6f/attachment.html>
More information about the llvm-bugs
mailing list