On Mon, Dec 28, 2009 at 12:15:10PM +0100, Aurelien Jarno wrote:
> On Mon, Dec 28, 2009 at 10:58:32AM +0200, Avi Kivity wrote:
> > On 12/28/2009 12:52 AM, Anthony Liguori wrote:
> > >
> > >As a reviewer, you can read qemu-commits to see when something has
> > >been committed.
> > >
> > >I have the s
On Mon, Dec 28, 2009 at 10:58:32AM +0200, Avi Kivity wrote:
> On 12/28/2009 12:52 AM, Anthony Liguori wrote:
> >
> >As a reviewer, you can read qemu-commits to see when something has
> >been committed.
> >
> >I have the same problem fwiw. I don't read qemu-commits because I
> >always look at the c
On Mon, Dec 28, 2009 at 10:58:32AM +0200, Avi Kivity wrote:
> On 12/28/2009 12:52 AM, Anthony Liguori wrote:
>>
>> As a reviewer, you can read qemu-commits to see when something has
>> been committed.
>>
>> I have the same problem fwiw. I don't read qemu-commits because I
>> always look at the
On 12/28/2009 12:52 AM, Anthony Liguori wrote:
As a reviewer, you can read qemu-commits to see when something has
been committed.
I have the same problem fwiw. I don't read qemu-commits because I
always look at the contents of origin when I fetch from it to see what
others are doing. Prac
On Mon, Dec 28, 2009 at 4:34 AM, Aurelien Jarno wrote:
> Most of the patches I commit without posting them first to the list are
> to fix bugs on non i386 targets, as they are broken too often by people
> who don't care about them.
>
> I don't like leaving the tree broken too long so I prefer to f
Am 27.12.2009 um 17:12 schrieb Blue Swirl:
On Sun, Dec 27, 2009 at 11:37 AM, Michael S. Tsirkin
wrote:
2. When a change is committed to the tree, often no notification is
sent
to the author.
Why is it a good idea to ask everyone to subscribe to qemu commits
list as well? Can 'applied
