public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Feng <ef2648@columbia.edu>
To: Martin Jambor <mjambor@suse.cz>
Cc: StevenSun2021@hotmail.com, David Malcolm <dmalcolm@redhat.com>,
	gcc@gcc.gnu.org
Subject: Re: Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension`
Date: Tue, 4 Apr 2023 10:31:40 -0400	[thread overview]
Message-ID: <CANGHATXp90txUEUEO2FjLAUmP60wkNX_MgSV+DFuntby1gCMwg@mail.gmail.com> (raw)
In-Reply-To: <ri6r0t12ddx.fsf@suse.cz>

Thanks Martin! Sounds good; I submitted my proposal unchanged for now
(i.e assuming an independent project), but as Dave mentioned in
another thread, it may be divided into several logical components,
perhaps with certain features extended, to be suited for
collaboration.

Best,
Eric





On Mon, Apr 3, 2023 at 11:29 AM Martin Jambor <mjambor@suse.cz> wrote:
>
> Hello,
>
> On Mon, Apr 03 2023, Eric Feng via Gcc wrote:
> > Hi Steven,
> >
> > I’m happy to collaborate on this project together — it would be great
> > to have your experience with CPython internals on the team.
> >
>
> While I normally welcome collaboration, please note that GSoC rules and
> reasonable caution dictate that the two project must not be dependent on
> one another.  I.e. if one of you, for any reason, could not finish your
> bits in time, it must not have severe adverse effects on the other.
>
> If mostly independent collaboration is possible (and David agrees),
> then sure, go ahead.
>
> Thanks for understanding,
>
> Martin

      reply	other threads:[~2023-04-04 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 14:47 Eric Feng
2023-04-03 15:28 ` Martin Jambor
2023-04-04 14:31   ` Eric Feng [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=CANGHATXp90txUEUEO2FjLAUmP60wkNX_MgSV+DFuntby1gCMwg@mail.gmail.com \
    --to=ef2648@columbia.edu \
    --cc=StevenSun2021@hotmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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).