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 7
Date: Tue, 4 Jul 2017 01:57:58 +0530 [thread overview]
Message-ID: <CAME+mvVRSovmXLDUzz8dNiruvLrXFv3iUifqXDm+HwQDu1mJpQ@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 are updates after the last
discussion, and will be posted with this update, along
with the patches of the function get_submodule_displaypath()
and for_each_submodule_list().
2. deinit: The patch was discussed in the last update, and
I still have to make the required changes to this patch.
3. summary: I'm still working on debugging this patch as
the are still some part where the patch isn't working as
expected.
4. foreach: Most of the time was spent in reading the repo-object
patch series. Also, currently I'm still confused about the
approach I have to take for carrying this out.
PLAN FOR WEEK-8 (4 July 2017 to 10 July 2017):
The main focus for this week will be to get the reviewed code merged
by sending new version after their review. Hence, I've attached
the patches which were recently review, after adding the
suggested changes, with this update. Other than that, there is still
lots of work related to porting left as follows:
1. foreach: I'll try to come up with an approach for the present
problem in the foreach patch, and get this discussed with
mentors as well as with Brandon Williams so that I can
get this subcommand ported.
2. summary: Currently, I'm still on debugging the patch. There are
parts of the patch which aren't running as expected and hence
it is taking more time to figure it out.
3. deinit: The patch was reviewed in the last update and I'm yet to
work on the improving the patches as suggested.
Apart from this, there still lie two submodule subcommands: 'add' and
'update' unported.
I'll try to completed as much as work related to porting but will
also, focus on improving the code completed so that it becomes good
for merging.
[1]: https://docs.google.com/document/d/1krxVLooWl--75Pot3dazhfygR3wCUUWZWzTXtK1L-xU/
Thanks,
Prathamesh Chavan
next reply other threads:[~2017-07-03 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 20:27 Prathamesh Chavan [this message]
2017-07-03 20:32 ` [GSoC][PATCH 1/5 v4] submodule--helper: introduce get_submodule_displaypath() Prathamesh Chavan
2017-07-03 20:32 ` [GSoC][PATCH 2/5 v4] submodule--helper: introduce for_each_submodule_list() Prathamesh Chavan
2017-07-03 20:32 ` [GSoC][PATCH 3/5 v4] submodule: port set_name_rev() from shell to C Prathamesh Chavan
2017-07-03 20:32 ` [GSoC][PATCH 4/5 v4] submodule: port submodule subcommand 'status' " Prathamesh Chavan
2017-07-03 20:32 ` [GSoC][PATCH 5/5 v4] submodule: port submodule subcommand 'sync' " Prathamesh Chavan
-- strict thread matches above, loose matches on Subject: below --
2016-06-13 8:06 [GSOC Update] Week 6 Pranit Bauva
2016-06-20 7:37 ` [GSOC Update] Week 7 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+mvVRSovmXLDUzz8dNiruvLrXFv3iUifqXDm+HwQDu1mJpQ@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).