From: Hrishikesh Kulkarni <hrishikeshparag@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>
Cc: "Martin Liška" <mliska@suse.cz>,
"Richard Biener" <richard.guenther@gmail.com>,
"Martin Jambor" <mjambor@suse.cz>, "Jan Hubicka" <hubicka@ucw.cz>
Subject: Re: GSOC 2018 - Textual LTO dump tool project
Date: Fri, 16 Mar 2018 13:44:00 -0000 [thread overview]
Message-ID: <CAL+0whQDxugK6PR0e9_8DMZiP2Yz0tpXLMC-puLpVSgeayJ_fA@mail.gmail.com> (raw)
In-Reply-To: <7851d70b-b85a-c0c6-820c-fd92f07898f5@suse.cz>
Hi,
Thanks Martin and Richard. I have uploaded the final proposal on GSOC
website. Meantime I will study makefiles and GNU Make in greater detail.
Regards,
Hrishikesh
On Thu, Mar 15, 2018 at 4:09 PM, Martin Liška <mliska@suse.cz> wrote:
> On 03/15/2018 09:45 AM, Richard Biener wrote:
> > Yes, I think it's fine to submit it - but let's ask the Mentor for the
> > project, Martin, for his
> > opinion first.
> >
> > Martin?
> >
> > Thanks,
> > Richard.
>
> Hi.
>
> Sorry for the delay and thanks to Richi who's been co-mentoring the
> project.
> I've just read the submission draft and it looks nice! Please submit it.
>
> Martin
>
prev parent reply other threads:[~2018-03-16 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 8:30 Hrishikesh Kulkarni
2018-02-25 9:47 ` Martin Jambor
2018-02-27 16:11 ` Richard Biener
2018-02-28 14:38 ` Martin Liška
2018-03-02 9:25 ` Hrishikesh Kulkarni
2018-03-02 9:48 ` Richard Biener
2018-03-02 13:01 ` Jan Hubicka
2018-03-06 13:30 ` Hrishikesh Kulkarni
2018-03-06 14:37 ` Richard Biener
2018-03-06 14:51 ` Jan Hubicka
2018-03-06 15:02 ` Jan Hubicka
2018-03-06 15:06 ` Richard Biener
2018-03-06 15:29 ` Jan Hubicka
2018-03-11 19:23 ` Hrishikesh Kulkarni
2018-03-12 11:16 ` Richard Biener
2018-03-13 4:30 ` Hrishikesh Kulkarni
2018-03-14 14:58 ` Richard Biener
2018-03-14 19:13 ` Hrishikesh Kulkarni
2018-03-15 8:46 ` Richard Biener
2018-03-15 10:39 ` Martin Liška
2018-03-16 13:44 ` Hrishikesh Kulkarni [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=CAL+0whQDxugK6PR0e9_8DMZiP2Yz0tpXLMC-puLpVSgeayJ_fA@mail.gmail.com \
--to=hrishikeshparag@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mjambor@suse.cz \
--cc=mliska@suse.cz \
--cc=richard.guenther@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).