Andrew Jones writes:
> On Tue, Oct 27, 2015 at 10:15:32AM +, Peter Maydell wrote:
>> Hi; it's been suggested to me that it would be helpful to have a
>> qemu-arm mailing list, along the lines of the existing qemu-ppc
>> and qemu-block lists. The idea would be to get people to cc the
>> list
On 27 October 2015 at 10:15, Peter Maydell wrote:
> Hi; it's been suggested to me that it would be helpful to have a
> qemu-arm mailing list, along the lines of the existing qemu-ppc
> and qemu-block lists. The idea would be to get people to cc the
> list with their ARM related patches, so it woul
On 27.10.2015 14:02, Edgar E. Iglesias wrote:
> On Tue, Oct 27, 2015 at 10:15:32AM +, Peter Maydell wrote:
>> Hi; it's been suggested to me that it would be helpful to have a
>> qemu-arm mailing list, along the lines of the existing qemu-ppc
>> and qemu-block lists. The idea would be to get peo
On 2015/10/27 19:02, Edgar E. Iglesias wrote:
> On Tue, Oct 27, 2015 at 10:15:32AM +, Peter Maydell wrote:
>> Hi; it's been suggested to me that it would be helpful to have a
>> qemu-arm mailing list, along the lines of the existing qemu-ppc
>> and qemu-block lists. The idea would be to get p
On 10/28/2015 02:49 AM, Pavel Fedin wrote:
> Hello!
>
>> Just to jump on and bead a dead horse, I am not OK with the idea of a
>> mailing list where patches might get reviewed and staged for pull
>> without the general population of qemu-devel being able to look first.
>
> Ok ok, i don't obje
Hello!
> Just to jump on and bead a dead horse, I am not OK with the idea of a
> mailing list where patches might get reviewed and staged for pull
> without the general population of qemu-devel being able to look first.
Ok ok, i don't object, Peter has already explained a similar thing to me, a
On 10/27/2015 07:16 AM, Peter Maydell wrote:
> On 27 October 2015 at 11:07, Pavel Fedin wrote:
>>> (Everything should still be cc'd to qemu-devel as well.)
>>
>> I would drop this requirement, except for stuff which could touch
>> core functionality (qom, qobject).
>
> This is a standard requi
On Tue, Oct 27, 2015 at 4:02 AM, Edgar E. Iglesias wrote:
> On Tue, Oct 27, 2015 at 10:15:32AM +, Peter Maydell wrote:
> > Hi; it's been suggested to me that it would be helpful to have a
> > qemu-arm mailing list, along the lines of the existing qemu-ppc
> > and qemu-block lists. The idea wo
On 27 October 2015 at 11:07, Pavel Fedin wrote:
>> (Everything should still be cc'd to qemu-devel as well.)
>
> I would drop this requirement, except for stuff which could touch
> core functionality (qom, qobject).
This is a standard requirement for all our sub-mailing lists --
not everybody is
Hello!
> The idea would be to get people to cc the
> list with their ARM related patches, so it would mostly act as
> a way for people to filter their mail to separate the ARM stuff
> out from the qemu-devel firehose.
I also vote for it. The main qemu-devel traffic is quite high, and not
every
On Tue, Oct 27, 2015 at 10:15:32AM +, Peter Maydell wrote:
> Hi; it's been suggested to me that it would be helpful to have a
> qemu-arm mailing list, along the lines of the existing qemu-ppc
> and qemu-block lists. The idea would be to get people to cc the
> list with their ARM related patches
On Tue, Oct 27, 2015 at 10:15:32AM +, Peter Maydell wrote:
> Hi; it's been suggested to me that it would be helpful to have a
> qemu-arm mailing list, along the lines of the existing qemu-ppc
> and qemu-block lists. The idea would be to get people to cc the
> list with their ARM related patches
Hi; it's been suggested to me that it would be helpful to have a
qemu-arm mailing list, along the lines of the existing qemu-ppc
and qemu-block lists. The idea would be to get people to cc the
list with their ARM related patches, so it would mostly act as
a way for people to filter their mail to se
13 matches
Mail list logo
