From: David Edelsohn <dje.gcc@gmail.com>
To: farhad <sarvari.farhad@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Contribution
Date: Mon, 14 Mar 2022 12:51:47 -0400 [thread overview]
Message-ID: <CAGWvnym6p=5XXd2+Pay6xj4VXHS-JmU_zbAbMvTAXF6cW9F2LQ@mail.gmail.com> (raw)
In-Reply-To: <CAOw3FZBNqs9LLAJ2Z_W-GXOmiKu43-h7ZvoCHcmU8QeRhsuyEQ@mail.gmail.com>
On Mon, Mar 14, 2022 at 4:37 AM farhad via Gcc <gcc@gcc.gnu.org> wrote:
>
> TO whom it may concern,
> I'm Farhad Sarvari and I have been working as a software engineer for more
> than 10 years and also have a strong background in c++ programming language.
> In addition I wrote a book about modern C++.
> <https://leanpub.com/cpplibrary-persian> I want to contribute to GCC
> development. It would be great if you provide more detail about how i can
> contribute.
> Thanks in advance. I'm looking forward to hearing from you.
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
>
> Best regards,
> Farhad
>
> --
> sent by Farhad
>
>
> --
> sent by Farhad
next prev parent reply other threads:[~2022-03-14 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOw3FZBzjtxEmbSMJDviD-td4bDM_mCMs9BQpk0SvK4EpR8N5g@mail.gmail.com>
2022-03-14 8:35 ` Fwd: Contribution farhad
2022-03-14 16:51 ` David Edelsohn [this message]
2022-12-14 15:32 Contribution Mohamed Atef
2022-12-15 14:47 ` Contribution Jason Merrill
2022-12-15 16:42 ` Contribution Paul Smith
[not found] <3CB6D448.45A4FE3E@knmi.nl.suse.lists.egcs>
2002-04-12 5:54 ` contribution Andi Kleen
2002-04-12 5:58 ` contribution Toon Moene
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 5:45 contribution Toon Moene
[not found] <Pine.GSO.4.31.0204112030350.15026-101000@boojum.suse.lists.egcs-patches>
2002-04-12 1:28 ` contribution Andi Kleen
2002-04-12 11:42 ` contribution Alexey Starovoytov
2002-04-12 15:15 ` contribution Toon Moene
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='CAGWvnym6p=5XXd2+Pay6xj4VXHS-JmU_zbAbMvTAXF6cW9F2LQ@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=sarvari.farhad@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 read-only IMAP folder(s) and NNTP newsgroup(s).