From: Martin Jambor <mjambor@suse.cz>
To: Omkar Mohanty <franzohouser@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GSoC Rust : Metadata exports for Rust frontend
Date: Wed, 29 Mar 2023 18:30:54 +0200 [thread overview]
Message-ID: <ri61ql75xkx.fsf@suse.cz> (raw)
In-Reply-To: <CAAxQJHvRTR_VDBz8BmC8oD2Uj1qH_Cu00j=KLu=edQYzPfEp_w@mail.gmail.com>
Hello,
we are delighted you found contributing to GCC interesting.
On Mon, Mar 27 2023, Omkar Mohanty via Gcc wrote:
> Hello GCC developers,
>
> I am Omkar Mohanty, currently an undergrad in CS. I have contributed to a
> number of open Source organizations for the past one year and I have one
> year experience programming in both Rust and C++. I have attached my
> proposal for GSoC 2023, I hope it meets the standards of GCC.
>
> link :
> https://docs.google.com/document/d/1CC6OdB3U1TK4e9enFbvjr4XCy2X0Ys_M22NnE5oy5Nc/edit?usp=sharing
>
I can see that you have already discussed the project on the gcc-rust
zulip, which for Rust projects is probably the better place. But thanks
for letting us know here as well and do not hesitate to ask here too if
you have any specific question about GCC in general.
Good luck,
Martin
prev parent reply other threads:[~2023-03-29 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 17:24 Omkar Mohanty
2023-03-29 16:30 ` Martin Jambor [this message]
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=ri61ql75xkx.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=franzohouser@gmail.com \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).