From: Jeff King <peff@peff.net>
To: Shanti Swarup Tunga <b112041@iiit-bh.ac.in>
Cc: git <git@vger.kernel.org>
Subject: Re: About GSoc idea.
Date: Thu, 26 Mar 2015 12:21:30 -0400 [thread overview]
Message-ID: <20150326162130.GE6564@peff.net> (raw)
In-Reply-To: <CABJeaiomjkc7dEpT8i0Ecxh41fjOdZFm+du=uf7azq1nJitiuQ@mail.gmail.com>
On Wed, Mar 25, 2015 at 08:36:41PM +0530, Shanti Swarup Tunga wrote:
> Duy Nguyen and Stephen Robin , the two developers worked
> on converting git-pull.sh to C code . But in the idea page it is
> written that we should start with git-pull.sh. Should I worked on
> "git-pull.sh" or other shell script for the GSoc.
You don't have to start with git-pull; the ideas page is mostly about
suggesting a direction. However, my impression was that the work that
has been done so far on git-pull is far from complete (I didn't look at
it closely, though). So there may be more to do there, too.
-Peff
PS You may try cc-ing people relevant to what you're posting, which is a
good way of making sure you get their attention.
prev parent reply other threads:[~2015-03-26 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 15:06 About GSoc idea Shanti Swarup Tunga
2015-03-26 16:21 ` Jeff King [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=20150326162130.GE6564@peff.net \
--to=peff@peff.net \
--cc=b112041@iiit-bh.ac.in \
--cc=git@vger.kernel.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 NNTP newsgroup(s).