[Qemu-devel] qemu-devel now defaults to reply-to "poster"

[Qemu-devel] qemu-devel now defaults to reply-to "poster"

[Anthony Liguori]

So now when you hit Reply-to-all, your mail client will include the 
person who sent the original mail.  This has been a frequently requested 
change.

Regards,

Anthony Liguori

Re: [Qemu-devel] qemu-devel now defaults to reply-to "poster"

[François Revol]

> So now when you hit Reply-to-all, your mail client will include the
> person who sent the original mail.  This has been a frequently
> requested
> change.
>

broken_mailing_lists_count++;

François.

Re: [Qemu-devel] qemu-devel now defaults to reply-to "poster"

[Avi Kivity]

Anthony Liguori wrote:
> So now when you hit Reply-to-all, your mail client will include the 
> person who sent the original mail.  This has been a frequently 
> requested change.
>

Thank you!

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

[Qemu-devel] Re: qemu-devel now defaults to reply-to "poster"

[Jan Kiszka]

Anthony Liguori wrote:
> So now when you hit Reply-to-all, your mail client will include the
> person who sent the original mail.  This has been a frequently requested
> change.
> 

Hurray!

I think we should now encourage proper CC'ing when posting patches, ie.
ask patch submitters to
 - add the related subsystem maintainer (if identifiable)
 - add the author of the commit that is about to be fixed, enhanceed,
   reverted etc.
 - add people who commented on / contributed to previous versions of the
   patch

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

Re: [Qemu-devel] Re: qemu-devel now defaults to reply-to "poster"

[François Revol]

> Anthony Liguori wrote:
> > So now when you hit Reply-to-all, your mail client will include the
> > person who sent the original mail.  This has been a frequently
> > requested
> > change.
> >
>
> Hurray!
>
> I think we should now encourage proper CC'ing when posting patches,
> ie.
> ask patch submitters to
>  - add the related subsystem maintainer (if identifiable)
>  - add the author of the commit that is about to be fixed, enhanceed,
>    reverted etc.
>  - add people who commented on / contributed to previous versions of
> the
>    patch

I thought the purpose of a mailing list was to handle the *list* of
people to **mail* to automatically... looks like offloading to humans
back...

Oh well.

François.

Re: [Qemu-devel] Re: qemu-devel now defaults to reply-to "poster"

[Jan Kiszka]

François Revol wrote:
>> Anthony Liguori wrote:
>>> So now when you hit Reply-to-all, your mail client will include the
>>> person who sent the original mail.  This has been a frequently 
>>> requested
>>> change.
>>>
>> Hurray!
>>
>> I think we should now encourage proper CC'ing when posting patches, 
>> ie.
>> ask patch submitters to
>>  - add the related subsystem maintainer (if identifiable)
>>  - add the author of the commit that is about to be fixed, enhanceed,
>>    reverted etc.
>>  - add people who commented on / contributed to previous versions of 
>> the
>>    patch
> 
> I thought the purpose of a mailing list was to handle the *list* of 
> people to **mail* to automatically... looks like offloading to humans 
> back...

This unfortunately only works (more or less) up to certain level of
topics you try to follow actively, often also across multiple lists.
Well, we would need reliable semantic filtering, I guess. If you have
such a tool, free for everyone, please tell us. For now the common
workaround is CC'ing.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

Re: [Qemu-devel] Re: qemu-devel now defaults to reply-to "poster"

[Jamie Lokier]

François Revol wrote:
> I thought the purpose of a mailing list was to handle the *list* of
> people to **mail* to automatically... looks like offloading to humans
> back...

Nice idea.

But it only works for low traffic lists and people who are not busy.

Your idea of a mailing list doesn't work for people who don't have
time to read the whole list, but who it's important to involve in
specific threads.

For example, someone reporting a bug should see the replies to their
specific report, but often they won't have time to check the whole
list every day for replies.  Same for things which touch subsystems
with specific maintainers.

Cc lets you make sure specific people are involved in specific
threads.  Nobody's created a mailing-list header
"X-This-Message-Is-Important-To-The-Following-People:" which you'd
need otherwise.

Cc does that job, and if you have a good mail setup then you don't see
the message twice, it just flags it as important to the named people.

Which is why most development lists use group-reply and Cc, and many
where it's not important (such as chat lists) use list-reply.

-- Jamie

Re: [Qemu-devel] Re: qemu-devel now defaults to reply-to "poster"

[Avi Kivity]

François Revol wrote:
> I thought the purpose of a mailing list was to handle the *list* of 
> people to **mail* to automatically... looks like offloading to humans 
> back...
>   

In addition to the other problems people mentioned, reply-to-list fails 
when someone who is not subscribed posts a question.  Everyone sees the 
reply except whoever was asking.


-- 
error compiling committee.c: too many arguments to function