From: Prathamesh Chavan <pc44800@gmail.com>
To: git <git@vger.kernel.org>
Cc: Stefan Beller <sbeller@google.com>,
Christian Couder <christian.couder@gmail.com>
Subject: [GSoC] Update: Week 3
Date: Tue, 6 Jun 2017 02:26:29 +0530 [thread overview]
Message-ID: <CAME+mvXACX7DejOKDJ=-qV8Ex9ZdYT4vXYV+7AeesaKYUk1sGw@mail.gmail.com> (raw)
SUMMARY OF MY PROJECT:
Git submodule subcommands are currently implemented by using shell script
'git-submodule.sh'. There are several reasons why we'll prefer not to
use the shell script. My project intends to convert the subcommands into
C code, thus making them builtins. This will increase Git's portability
and hence the efficiency of working with the git-submodule commands.
Link to the complete proposal: [1]
Mentors:
Stefan Beller <sbeller@google.com>
Christian Couder <christian.couder@gmail.com>
UPDATES:
As planned for the third week, most of the time was spent on improving the
conditions of the present patches, which deal with porting the following
submodule subcommands:
1. foreach: After a discussion over the issue of the path variable in
windows, in this week my mentor, Stefan Beller came up with the
appropriate solution for the problem after discussing it with Ramsay
Jones. It is being posted on the mailing list for further discussion on
including it.[2]
Also, some changes are suggested to the posted version of ported foreach
function which needs to be taken care of.[3]
2. status: The subcommand's porting is completed and has been discussed
with the mentors for the last two week after which, a new version of the
ported function is posted on the mailing list.[4][5]
3. sync: The subcommand's porting is completed and I am currently discussing
it with my mentors for improving the ported function.
4. summary: Porting of this subcommand is underway and will be trying to
finish it in the following week.
PLAN FOR WEEK-4 (6 June 2017 to 12 June 2017):
1. sync: since this ported function is currently under discussion with
the mentors, firstly I'll be looking forward to improvising it as
suggested and do the needful changes.
2. ported function on the mailing list: currently the ported functions
foreach and status are on the mailing list, under discussion.
I will be updating the patches on the list and improvising
them as required for eventually getting these merged.
3. summary and deinit: I will resume porting submodule subcommands
from shell to C, firstly git-submodule summary and then git-submodule
deinit for this week.
[1]: https://docs.google.com/document/d/1krxVLooWl--75Pot3dazhfygR3wCUUWZWzTXtK1L-xU/
[2]: https://public-inbox.org/git/20170603003710.5558-1-sbeller@google.com/
[3]: https://public-inbox.org/git/20170602112428.11131-2-pc44800@gmail.com/
[4]: https://public-inbox.org/git/20170605202529.22959-1-pc44800@gmail.com/
[5]: https://public-inbox.org/git/20170605202529.22959-2-pc44800@gmail.com/
Thanks,
Prathamesh Chavan
next reply other threads:[~2017-06-05 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 20:56 Prathamesh Chavan [this message]
2017-06-05 22:25 ` [GSoC] Update: Week 3 Stefan Beller
-- strict thread matches above, loose matches on Subject: below --
2016-05-15 17:45 [GSOC Update] Week 2 Pranit Bauva
2016-05-22 19:58 ` [GSoC Update] Week 3 Pranit Bauva
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAME+mvXACX7DejOKDJ=-qV8Ex9ZdYT4vXYV+7AeesaKYUk1sGw@mail.gmail.com' \
--to=pc44800@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).