This has been proposed multiple times in the past (please search the
list archive at http://groups.google.com/group/django-users/), and it
was decided not to add a prefix to the subject line; any good mail
client, including GMail (which you seem to be using, judging by your
email address) can filter on arbitrary headers in messages, so a much
better solution that doesn't clutter up subject lines is to filter
messages based on 'To: django...@googlegroups.com'.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
Most mailing lists follow that convention... for instance see all of the
openSUSE mailing lists... and zillions of others. The practice is not
difficult, doesn't really clutter the subject line all that much, and
benefits much of the community.
I concur with the idea. ~please...
--
Kind regards,
M Harris <><
>> This has been proposed multiple times in the past (please search the
>> list archive at http://groups.google.com/group/django-users/), and it
>> was decided not to add a prefix to the subject line; any good mail
>> client,
> The reason it gets proposed multiple times is because it is a good
> practice
> and a very good idea...
the point is that the people who run the list get to choose - and
they have chosen not to, so it is pointless discussing this (i was
one of the first proposers, btw)
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
Every mailing list I've ever seen that uses prefixed subjects adds the prefix
automatically. Users shouldn't be bothered to add a repetitive prefix to their
emails. We have machines to do that sort of stuff.
More over, you shouldn't expect others to accomodate what appears to be severe
deficiencies in your mail clients ability to deal with SPAM and sort incoming
messages (or your inability to properly configure those features).
One thing that I think would be nice, however, is if MIME digests were support
by Google groups. I guess you can't get everything you want.
-Forest
It's a waste of 14 characters if it's [django-users], and 7 as [django],
now, when you get people with broken mail clients that also keep
prepending Re: then those 14 characters become very important - my
terminal is usually only about 80 characters long, most of the time I
can only see around 20/25 characters of the subject line, I'd really
rather that they were all relevant than to lose them to an unneeded
prefix.
Thanks,
--
Brett Parker
List-Id: <django-users.googlegroups.com>
^ That's a better header to match on, IMO, then if the list is
CC'd/BCC'd you'll still have the mail sorted in to the right folder
(it's how I sort all list traffic). Any mailing list without a List-Id
header probably isn't worth reading anyways!
Cheers,
--
Brett Parker
Adding prefixes to list mails is purely redundant, since any good
email client can already sort email into folders or automatically
apply labels based on headers, and it creates a usability problem.
Consider someone who doesn't have a 2400-pixel wide maximized email
client, and who sees this set of subject lines:
[django-users] Problem with m
[django-users] Needing help wi
And compare to:
Problem with mod_python
Needing help with sessions
Which one is more useful?
Again: the proposal has come up multiple times and has been shot down
multiple times. Is it really worth expending energy to argue with
something that's not important at all in the long run, and which won't
be changed at all by the arguing? ;)
I'd say it's time to change your mutt config :)
Unless you need to know the kb's in each and every message, that is.
-Forest