From: David Edelsohn <dje.gcc@gmail.com>
To: VAISHNAVI DAYANAND <vaishnavi_d@ec.iitr.ac.in>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: how to get started with contribution
Date: Sat, 29 Jan 2022 11:06:10 -0500 [thread overview]
Message-ID: <CAGWvnynqiYfPEivHu7xRXKKWYddf5E3rgLj05NKk589WyAK+Cw@mail.gmail.com> (raw)
In-Reply-To: <CAALJv7DO3ALe=LMC0tqedZupz5BobkBHhkGo5j4NQ9Lw5iEwLQ@mail.gmail.com>
On Sat, Jan 29, 2022 at 10:37 AM VAISHNAVI DAYANAND via Gcc
<gcc@gcc.gnu.org> wrote:
>
> Respected sir/madam,
> I am Vaishnavi Andhalkar, a junior undergrad at IIT Roorkee. I have
> recently started contributing to open source, and I am new at it. But, I am
> well aware of C++, programming and algorithms, and javascript. I would like
> to contribute to your organization. Would you please tell me how to get
> started?
> Hoping to hear from you soon
> Thanks and Regards
> Vaishnavi
Thanks for your interest in GCC. Welcome!
A good place to start is the GCC Wiki Getting Started page:
https://gcc.gnu.org/wiki/#Getting_Started_with_GCC_Development
and browse other recent answers to similar questions in the archives
of this mailing list.
Thanks, David
next prev parent reply other threads:[~2022-01-29 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 15:35 VAISHNAVI DAYANAND
2022-01-29 16:06 ` David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-19 7:44 How to get started with Contribution Purvak Baliyan
2022-02-19 15:13 ` David Edelsohn
2022-01-15 10:05 How to get started with contribution Purvak Baliyan
2022-01-15 14:10 ` David Edelsohn
2022-01-05 20:26 Prakhar Khandelwal
2022-01-05 20:35 ` David Edelsohn
2021-12-04 10:02 Om Kenge
2021-12-04 10:50 ` Jonathan Wakely
2021-11-23 13:21 Om Kenge
2021-11-23 13:40 ` Jonathan Wakely
2021-11-20 10:05 parth rastogi
2021-11-20 10:42 ` Jonathan Wakely
2021-11-20 13:05 ` parth rastogi
2021-11-09 7:03 Anmol Singh
2021-11-10 11:49 ` Mark Wielaard
2021-11-10 12:07 ` Jonathan Wakely
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=CAGWvnynqiYfPEivHu7xRXKKWYddf5E3rgLj05NKk589WyAK+Cw@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=vaishnavi_d@ec.iitr.ac.in \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).