In response to "Mikkel Høgh" <mikkel@xxxxxxxxx>: > > On 17/10/2008, at 12.24, Tomasz Ostrowski wrote: > > > On 2008-10-17 12:13, Mikkel Høgh wrote: > > > >>> You're supposed to use "Reply to all" if you want to reply to the > >>> list. > >> > >> Well, I think the most common use case for a mailing list is to reply > >> back to the list, isn't that the whole point? > > > > It is a point of having "Reply to all" button. With "reply-to" is it > > hard to reply to one person, easy to reply to the list. Without it > > it is > > both easy. > > But again, how often do you want to give a personal reply only? That > is a valid use-case, but I'd say amongst the hundreds of mailing-list > replies I've written over the years, only two or three were not sent > back to the mailing list. You're forgetting the cost of a mistake in that case. As it stands, if you hit reply when you meant reply-to, oops, resend. If it's changed and you hit reply when you want to send a private message to the poster, you just broadcast your private message to the world. > Yay, even more manual labour instead of having the computers doing the > work for us. What's your next suggestion, go back to pen and paper? Don't be an asshole. There's no need for that kind of cynicism. > Well, my point is that Reply-To: is only dangerous if you're not > careful. Not so with the other examples you mention :) But as it is now, it's not dangerous at all. > If you're writing something important, private and/or confidential, > don't you always check before you send? You'd better, because a small > typo when you selected the recipient might mean that you're sending > love-letters to your boss or something like that :) I'd rather know that the computer had my back in the case of an error, instead of it helping me mindlessly even when I'm doing the wrong thing. To me, that's also the difference between MySQL and PostgreSQL. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@xxxxxxxxxxxxxxxxxxxxxxx Phone: 412-422-3463x4023 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
