> On 01/28/2013 07:45 PM, Tanya Lattner wrote: >> I will be removing the list prefix "LLVMDev" from the subject line. If >> you are filtering by this, please use the list headers instead. >> >> If you have any questions, please let me know. > > Thanks Tanya, this makes the subject lines of the commits a lot more > accessible. > > TobiPlease let me state my opinion against this change. Due to the heavy traffic on LLVM mailing lists, one needs some kind of filtering to keep only the relevant emails in the inbox. Since my ISP's email server doesn't support any server-side email filtering, I used to filter the e-mails visually. It was easy to ignore emails with the subject prefixed with LLVM or cfe (or both). Right now I can only see 200 emails in my inbox and I cannot distinguish between them. I personally also preferred the file names in the subject, since that allowed me to visually filter the commits in my areas. However, if we all start prefixing the commit messages with the area (as some already do), this problem is gone. Nuno
On Jan 29, 2013, at 12:11 PM, Nuno Lopes <nunoplopes at sapo.pt> wrote:>> On 01/28/2013 07:45 PM, Tanya Lattner wrote: >>> I will be removing the list prefix "LLVMDev" from the subject line. If you are filtering by this, please use the list headers instead. >>> >>> If you have any questions, please let me know. >> >> Thanks Tanya, this makes the subject lines of the commits a lot more accessible. >> >> Tobi > > Please let me state my opinion against this change. > Due to the heavy traffic on LLVM mailing lists, one needs some kind of filtering to keep only the relevant emails in the inbox. Since my ISP's email server doesn't support any server-side email filtering, I used to filter the e-mails visually. It was easy to ignore emails with the subject prefixed with LLVM or cfe (or both). > Right now I can only see 200 emails in my inbox and I cannot distinguish between them. > > I personally also preferred the file names in the subject, since that allowed me to visually filter the commits in my areas. However, if we all start prefixing the commit messages with the area (as some already do), this problem is gone.I understand the challenge with no server-side filtering. I believe the goal is to prefix the commit messages with even more specific prefixes to note what area has changed. Those who send patches should be using [PATCH] in their subject, but we can't force people to. A strong reason for the change was that most subject lines had multiple prefixes, and the list name was really not necessary. While not a perfect solution, you could do some client side filtering (procmail or builtin filters in mail clients) that might help you out a bit. Your objection is noted and we can re-evaluate the change as we get more feedback from the community. -Tanya
On Tue, Jan 29, 2013 at 12:11 PM, Nuno Lopes <nunoplopes at sapo.pt> wrote:>> On 01/28/2013 07:45 PM, Tanya Lattner wrote: >>> >>> I will be removing the list prefix "LLVMDev" from the subject line. If >>> you are filtering by this, please use the list headers instead. >>> >>> If you have any questions, please let me know. >> >> >> Thanks Tanya, this makes the subject lines of the commits a lot more >> accessible. >> >> Tobi > > > Please let me state my opinion against this change. > Due to the heavy traffic on LLVM mailing lists, one needs some kind of > filtering to keep only the relevant emails in the inbox. Since my ISP's > email server doesn't support any server-side email filtering, I used to > filter the e-mails visually. It was easy to ignore emails with the subject > prefixed with LLVM or cfe (or both). > Right now I can only see 200 emails in my inbox and I cannot distinguish > between them. > > I personally also preferred the file names in the subject, since that > allowed me to visually filter the commits in my areas. However, if we all > start prefixing the commit messages with the area (as some already do), this > problem is gone. >Could you clarify your situation? Can't you look at a message's headers and see which mailing list it's addressed to / came from? That enables setting up client filters to sort messages into folders / apply filters, etc. Eli
On 1/29/2013 2:49 PM, Tanya Lattner wrote:> > Your objection is noted and we can re-evaluate the change as we get more feedback from the community.I'm at the other end of this. For me this change would work great. I use Thunderbird to read this list, and I assign emails to folders based on the "List-Id" header. In a TB window of a regular (usable) size, the word "[LLVMDev]" occupies 1/3 of the subject space. I would much prefer to be able to see more of the actual content of the subject. I know this is about a different ML, but llvm-commits was even worse. The subject of a typical email looked like this: "[llvm-commits] [llvm] r123456 - /llv..." -Krzysztof -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
Quoting Eli Bendersky <eliben at google.com>:> On Tue, Jan 29, 2013 at 12:11 PM, Nuno Lopes <nunoplopes at sapo.pt> wrote: >>> On 01/28/2013 07:45 PM, Tanya Lattner wrote: >>>> >>>> I will be removing the list prefix "LLVMDev" from the subject line. If >>>> you are filtering by this, please use the list headers instead. >>>> >>>> If you have any questions, please let me know. >>> >>> >>> Thanks Tanya, this makes the subject lines of the commits a lot more >>> accessible. >>> >>> Tobi >> >> >> Please let me state my opinion against this change. >> Due to the heavy traffic on LLVM mailing lists, one needs some kind of >> filtering to keep only the relevant emails in the inbox. Since my ISP's >> email server doesn't support any server-side email filtering, I used to >> filter the e-mails visually. It was easy to ignore emails with the subject >> prefixed with LLVM or cfe (or both). >> Right now I can only see 200 emails in my inbox and I cannot distinguish >> between them. >> >> I personally also preferred the file names in the subject, since that >> allowed me to visually filter the commits in my areas. However, if we all >> start prefixing the commit messages with the area (as some already do), this >> problem is gone. >> > > Could you clarify your situation? Can't you look at a message's > headers and see which mailing list it's addressed to / came from? That > enables setting up client filters to sort messages into folders / > apply filters, etc.My point was that not everyone uses gmail nor everyone has access to nice email servers that perform server-side filtering. Of course I can do all these things in the client, but my webmail client is dumb. So this change is very frustrating to me since I cannot *visually* filter LLVM emails anymore (and by visually I mean reading the prefix of the subjects). I'm usually absent from bikeshedding discussions, but this time I'm really frustrated with the change.. Nuno