On 03/09/15 17:31, Brian J. Johnson wrote: > On 03/09/2015 10:40 AM, Laszlo Ersek wrote:
>> I also support David's recommendations: dropping the [edk2] subject >> prefix, and (especially!) the obnoxious Reply-To header, exactly for the >> reasons David named. > > Personally, I like the Reply-To header. With it, using Thunderbird, > replies go to the list automatically. Without it, I need to "reply all" > then edit the "To:" header if I want to reply only to the list. If I > just "reply", it only goes to the original sender. I find I reply to > the list far more often than to an individual, so the Reply-To is handy > for me. This difference of opinion seems to be rooted in different workflows then :) In general, most upstream development lists strongly discourage replying to the list only. Followup should be sent either in private only, or (much more commonly) to both sender *and* list. There are two reasons for this (ie. the latter part): - Sometimes people who are not subscribed post to the list. This should be actively supported. They will only receive the entirety of the feedback from the regular subscribers if everyone who responds keeps them CC'd by name. For example, this is how I occasionally post to qemu-devel, and (extremely rarely) to libvir-list. - Filtering into folders, for regular subscribers. Normal list traffic goes into the list-specific folder on the subscriber side; this way a subscriber can follow discussions as a "bystander", or just archive them for later. However, when a subscriber is also the submitter (thread starter), or someone else adds him/her as a recipient by name, in another discussion, then *beside* having a complete archive in the list-specific folder, the subscriber will get *personally* addressed copies in his / her INBOX. This is extremely important for high traffic lists -- I want the full archive in my list-specific folder "for later, if I need it", even with the messages that I myself sent or received, plus I want the messages that directly need my attention in my INBOX. I know that Debian lists for example have a policy where people are allowed to reply to the list only. That policy cannot distinguish the "bystander subscriber" from the "personally affected subscriber". edk2-devel is the only upstream development list I know of that's been doing this "wrong". (For example, this email of mine should reach you both directly and through the list, but it won't, because of the Reply-To header. I could re-add you, and sometimes I do that, but most of the time I don't bother. It's not right.) Thanks! Laszlo ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
