[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] hw/display contains files named *_template.h. T

From: John Snow
Subject: Re: [Qemu-devel] [PATCH] hw/display contains files named *_template.h. These are included many times with different values of the DEPTH macro. However, only the DEPTH == 32 case is used. Removed support for DEPTH != 32 in the template headers and in the file that include them.
Date: Mon, 28 Mar 2016 16:11:39 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

On 03/27/2016 03:33 AM, Nutan Shinde wrote:
> Hi,
> So, this patch won't be considered, because there is already a patch
> related to the same issue, right?

You'd have to follow the other thread to see if the patch was accepted
or not. Even if it isn't, etiquette is generally that it'd be rude to
not allow them a chance to spin their own v2/revision.

So if your patch was sent later than theirs, it's likely this one won't
be considered, correct.


> On Wed, Mar 23, 2016 at 7:40 PM, John Snow <address@hidden
> <mailto:address@hidden>> wrote:
>     On 03/23/2016 01:30 AM, Nutan Shinde wrote:
>     > Hi John,
>     >
>     > My patch is same as the patch mentioned in the link. I just picked up
>     > the task from BitSizedTask page, as it was not crossed.
>     >
>     > I guess the issue is resolved then, what should I do in this case?
>     Also,
>     > please tell me, how do I know which tasks are already taken up?
>     >
>     > Regards,
>     > Nutan Shinde.
>     >
>     In some cases, since GSoC and Outreachy are approaching, a lot of people
>     are trying to pick off the Bite Sizes Tasks right now. You may do well
>     by checking
>     https://lists.nongnu.org/archive/html/qemu-devel/2016-03/threads.html to
>     make sure that nobody else has submitted a fix for the task you wish
>     to fix.
>     In some cases, fixes may have been submitted recently, but aren't
>     accepted into QEMU just yet. Searching the list archives will help you
>     determine which is which.
>     Thanks,
>     --js

reply via email to

[Prev in Thread] Current Thread [Next in Thread]