public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: shivansh khare <khareshivansh03@gmail.com>
To: Ankur Saini <arsenic.secondary@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Seeking to contribute to your organisation
Date: Sat, 11 Feb 2023 17:31:10 +0530	[thread overview]
Message-ID: <CABjncYhkzLURbYaZzpERciMVq47fSbbNrQTmjHFKViBopQtUtQ@mail.gmail.com> (raw)
In-Reply-To: <2A84CF75-6D1A-4112-817C-9A1D6C320F67@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

Thanks for the tip!


On Sat, 11 Feb, 2023, 5:19 pm Ankur Saini, <arsenic.secondary@gmail.com>
wrote:

> That wiki page also recommends to "put "GSoC" somewhere to the
> subject”.
> Doing so should improve visibility of the message and make
> it reach those who filter out GSoC related mails and ultimately help
> you getting a faster and better reply from the community. :)
>
> - Ankur
>
> > On 09-Feb-2023, at 8:37 PM, shivansh khare via Gcc <gcc@gcc.gnu.org>
> wrote:
> >
> > Hello,
> >
> > I would like to ask whether I could be part of the upcoming GSoC. I have
> > been wanting to contribute to the project for some time now and I think
> > that this would be a nice opportunity for that.
> >
> > I have looked into the different starter projects that are offered in the
> > [Wiki GSoC page](https://gcc.gnu.org/wiki/SummerOfCode) and I was
> > particularly interested in the `-ftime-trace` project. The following is
> > what is given as a short description about the problematic:
> > "Implement something similar to Clang's -ftime-trace feature which
> > generates performance reports that show where the compiler spends compile
> > time. For more information, please check the following blog post. There's
> > also an existing bugzilla entry for this (if this becomes a GSoC project,
> > the assignee will of course change). Required skills include C/C++ and
> > finding a way through a large code-base."
> >
> > I am looking forward to your response.
> >
> > Best regards,
> > Shivansh Khare
>
>

      reply	other threads:[~2023-02-11 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 15:07 shivansh khare
2023-02-11 11:49 ` Ankur Saini
2023-02-11 12:01   ` shivansh khare [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=CABjncYhkzLURbYaZzpERciMVq47fSbbNrQTmjHFKViBopQtUtQ@mail.gmail.com \
    --to=khareshivansh03@gmail.com \
    --cc=arsenic.secondary@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).