From: John Snow <jsnow@redhat.com>
To: Nutan Shinde <nutanshinde1992@gmail.com>
Cc: qemu-devel@nongnu.org
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: Wed, 23 Mar 2016 10:10:56 -0400 [thread overview]
Message-ID: <56F2A3F0.7030006@redhat.com> (raw)
In-Reply-To: <CADyday2Xmo92OWXGQzvrMC_u-DZxcLBn1QMggdqEm1AsuZXx1A@mail.gmail.com>
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
next prev parent reply other threads:[~2016-03-23 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 6:34 [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 Nutan Shinde
2016-03-22 22:04 ` John Snow
2016-03-23 5:30 ` Nutan Shinde
2016-03-23 14:10 ` John Snow [this message]
2016-03-27 7:33 ` Nutan Shinde
2016-03-28 20:11 ` John Snow
2016-03-22 22:09 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F2A3F0.7030006@redhat.com \
--to=jsnow@redhat.com \
--cc=nutanshinde1992@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).