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 5
Date: Tue, 20 Jun 2017 03:11:06 +0530 [thread overview]
Message-ID: <CAME+mvUQJFneV7b1G7zmAidP-5L=nimvY43V0ug-Gtesr83tzg@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:
Following are the updates about my ongoing project:
1. sync and status: The patches were discussed with the mentors
and after that, are being posted with this patch.
2. deinit: The patch is finally debugged, and is ready to be
discussed. It is also attached with this update.
3. summary: While porting the subcommand, I underwent certain
issues. After getting them clarified from my mentors, I
have resumed working on it. I'm aware of the time I have
taken for porting this subcommand is more than the previous
ones. Hence will try my best to finish this in this week.
4. foreach: As stated in the previous update, the subcommand was
ported without resolving the bug, and simply translating the
present code, and adding a NEEDSWORK tag to the comment for
mentioning the reported bug as well.
But as communicating between child_process is still an issue
and so there was no simple was to current carry out the
porting. And hence, a hack was used instead. But after
discussing it, instead using the repository-object patch
series will help to resolve these issues in this situation.
PLAN FOR WEEK-6 (20 June 2017 to 26 June 2017):
1. summary: Mostly I'll be working on this and post the patch
for discussion as soon as possible.
2. foreach: As it was decided that unblock the conversion of
this submodule subcommand, the original cmd_foreach was
ported without including the BUG-FIX patch here.
Hence, for this week I will try to utilize the
'repository-object' series by Brandon Williams.
3. deinit: I will be working on improvising this patch as it was
recently debugged and posted for discussion.
[1]: https://docs.google.com/document/d/1krxVLooWl--75Pot3dazhfygR3wCUUWZWzTXtK1L-xU/
Thanks,
Prathamesh Chavan
next reply other threads:[~2017-06-19 21:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 21:41 Prathamesh Chavan [this message]
2017-06-19 21:50 ` [GSoC][PATCH 1/6] dir: create function count_slashes Prathamesh Chavan
2017-06-19 21:50 ` [GSoC][PATCH 2/6] submodule--helper: introduce get_submodule_displaypath and for_each_submodule_list Prathamesh Chavan
2017-06-20 18:22 ` Brandon Williams
2017-06-22 7:01 ` Christian Couder
2017-06-19 21:50 ` [GSoC][PATCH 3/6] submodule: port set_name_rev from shell to C Prathamesh Chavan
2017-06-19 21:50 ` [GSoC][PATCH 4/6] submodule: port submodule subcommand status Prathamesh Chavan
2017-06-20 18:44 ` Brandon Williams
2017-06-19 21:50 ` [GSoC][PATCH 5/6] submodule: port submodule subcommand sync from shell to C Prathamesh Chavan
2017-06-20 17:35 ` Stefan Beller
2017-06-22 6:50 ` Christian Couder
2017-06-19 21:50 ` [GSoC][PATCH 6/6] submodule: port submodule subcommand 'deinit' " Prathamesh Chavan
2017-06-20 17:20 ` [GSoC][PATCH 1/6] dir: create function count_slashes Stefan Beller
2017-06-20 0:01 ` [GSoC] Update: Week 5 Andrew Ardill
2017-06-20 0:38 ` Brandon Williams
2017-06-26 23:24 ` Prathamesh Chavan
-- strict thread matches above, loose matches on Subject: below --
2016-05-30 5:37 [GSOC Update] Week 2 Pranit Bauva
2016-06-06 6:53 ` [GSOC Update] Week 5 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+mvUQJFneV7b1G7zmAidP-5L=nimvY43V0ug-Gtesr83tzg@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).