Brendan Jurd wrote: > > Another is that the email list provides a > > "push" mechanism for putting the proposed patch under the noses of a > > bunch of people, a few of whom will hopefully take a sniff ;-). > > A tracker is very much more of a "pull" scenario where someone has to > > actively go looking for pending/proposed changes. > > > > The typical way to solve this is to have the tracker send an automatic > notification email to a list saying "Hey, there's a new ticket at , > come and check it out". > > This is trivial to configure in a "real" tracker. Less so for a wiki > page, but it could still be accomplished with the careful application > of script-fu.
Not sure how others feel, but automated emails of "come see my new stuff" are kind of annoying if you get alot of them because you can't actually act on the email itself --- you have to take the step of going to the web site, which may be OK if they are clickable links, but you do end up hopping in and out of email. And if you read something on the web site then get an email it is hard to know if you have seen that entry already. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers