From: Thomas Huth <thuth@redhat.com>
To: Rohit Shinde <rohit.shinde12194@gmail.com>, qemu-devel@nongnu.org
Cc: jsnow@redhat.com, ehabkost@redhat.com, crosa@redhat.com
Subject: Re: Contributor wanting to get started with simple contributions
Date: Tue, 25 Aug 2020 07:50:59 +0200 [thread overview]
Message-ID: <2d69f1ac-df97-9d70-d2e2-e9cf27cf9b0c@redhat.com> (raw)
In-Reply-To: <CA+Ai=tBJqLB7yDbd-kqzDhr+d+65K9r3DQsZrB2kGi9wF8BaiA@mail.gmail.com>
On 25/08/2020 04.26, Rohit Shinde wrote:
> Hey John,
>
> I sent this email a couple of weeks ago to the qemu mailing list since I
> didn't really know who to approach.
Hi Rohit,
The qemu-devel mailing list is very high traffic. So I'm sorry, but you
might need to be a little bit more specific with your questions if you
expect an answer...
> I have built qemu from source and I have my machine setup for
> git-publish via email.
>
> I would like to start contributing with one of the bite sized tasks
> mentioned in the wiki page. The one that interests me and which I
> think is the easiest are the sections on "Compiler Driven Cleanup"
> and "Dead Code Removal". I think this is a good way to get
> introduced to the codebase.
Sure, just go ahead and have a try! Once you've successfully wrote a
patch, please have a look at
https://wiki.qemu.org/Contribute/SubmitAPatch how to submit it.
> I plan to stay and become a long term contributor. Is there any CS
What does "CS" stand for?
> theory that I would need to know other than what I mentioned above?
> Is it possible to "learn on the go"?
You certainly have to "learn on the go", since it is likely quite
impossible to grasp a huge project like QEMU at once.
Cheers,
Thomas
next prev parent reply other threads:[~2020-08-25 5:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 11:18 Contributor wanting to get started with simple contributions Rohit Shinde
2020-08-25 2:26 ` Rohit Shinde
2020-08-25 5:50 ` Thomas Huth [this message]
2020-08-26 15:00 ` Rohit Shinde
2020-08-26 15:51 ` John Snow
2020-08-26 17:55 ` Rohit Shinde
2020-08-29 5:14 ` Rohit Shinde
2020-09-02 16:38 ` Rohit Shinde
2020-09-30 4:38 ` John Snow
2020-10-13 18:46 ` Rohit Shinde
2020-10-14 17:59 ` John Snow
2020-08-27 4:37 ` Thomas Huth
2020-08-28 0:49 ` Rohit Shinde
2020-08-28 4:14 ` Thomas Huth
2020-08-26 15:40 ` John Snow
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=2d69f1ac-df97-9d70-d2e2-e9cf27cf9b0c@redhat.com \
--to=thuth@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rohit.shinde12194@gmail.com \
/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).