On 2001.06.03, Jim Wilcoxson <[EMAIL PROTECTED]> wrote:
> I have a suggestion: these Source Forge cc's to the mailing list are kinda
> nice in that it connects the two forms of communication and helps keep the
> community tied together.
>
> But would it be possible to either:
>
> a) only post the new responses to the non-digest mailing list, or
> b) only post updated items on the digest mailing list, or
It is annoying that the "Initial Comment" gets sent over and over.
Perhaps you'd like to go to http://sf.net/projects/alexandria and
open a Feature Request ticket as an enhancement for SourceForge?
Only tickets that have activity (a status change, a new comment,
etc.) get mailed, so any time you see mail come across, it's because
there was SOME activity on the ticket.
> c) show the latest update at the beginning of the message
d) Create seperate mailing lists for the different trackers.
These are the names I propose:
AOLSERVER-BUGS, AOLSERVER-SUPPORT, AOLSERVER-FEATURE-REQUESTS
Then, people who want the relevant noise can subscribe to it.
(I also would like to se an AOLSERVER-DEV mailing list for
developer noise, but the general AOLSERVER list seems to be
covering that, so no worries yet.)
> It gets old seeing the same thing come across the mailing list over and
> over, to the point where I'm about ready to disable them.
This is why sending the SourceForge automated emails to seperate
mailing lists may be useful.
In the meantime, I suggest that you may want to investigate how
to create filtering rules within your email client (or mail
transport agent) to put messages that match the expression
"[ aolserver-.*-[0-9]* ]" in the Subject: header into a seperate
mail folder, so you won't be bothered by them (and can check them
when you feel like it).
- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
