From: Peter S. <pe...@st...> - 2012-04-19 19:14:02
|
Ethan Dicks wrote: > I don't see a problem with lack of content in the subject lines and > I'm on enough mailing lists that I don't find "[Libusb-devel]" > annoyingly redundant. The redundant part is that it's there on every mail to the list. :) > > IMO it's been broke for a long time, but of course by now we're all > > used to it. Possibly there is a way for you to use (other) headers > > to identify libusb email? > > For me, using headers means setting up filters, in which case, I will > probably bin all libusb-devel traffic since I would have to go > somewhere other than my inbox to deal with it. What I personally do is look at list-recipient. I understand that not all mail programs can show that, but maybe they have other ways to mark email, so that it still has a distinct look where you want it to be. > I am against the change, but as long as I can see a specific string in > every subject line that tells me what list the message is from, I'll > live with it. Thanks for the input! > I subscribe to over a dozen technical mailing lists. Yes, me too. > The standard is "[listname]" at the front of the subject. It's a de-facto standard only because it is the default setting in mailman, not because every list administrator and list subscriber has opted-in. > I use the tag to prioritize what to read and what to delete unread > based on the rest of the subject line. The tag helps give me > context to evaluate the relevance of that subject. Nod. I find subjects alone don't work too well, because discussions often change along the way. But sure, if the subject is the only data you can use very easily then I understand that the context matters. > So, please don't change it, but if you must, at least leave > "libusb" on the subject line. Hopefully more people will say if they absolutely can't go without the prefix. //Peter |