mailing list mirror (one of many)
 help / Atom feed
From: Prathamesh Chavan <>
To: git <>
Cc: Christian Couder <>,
	Stefan Beller <>
Subject: [GSoC] Update: Week-13
Date: Wed, 16 Aug 2017 04:34:21 +0530
Message-ID: <> (raw)


Git submodule subcommands are currently implemented by using shell script
''. 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]

Stefan Beller <>
Christian Couder <>


Following are the updates about my ongoing project:

* add: most of the time of the week was spent in debugging the
  ported submodule subcommand functions. But, even after so,
  currently the ported functions fail in total 15 tests from
  the test suit. The WIP patches have been updated regularly,
  and currently the patch is under discussion with the mentors
  as well. The current status of the patch is pushed on github as
  well, and can be viewed at:[2]

Since the rest of the patches were almost the same as that in the
previous update(except for the 'summary' patch, which was last
updated after Christian's review), the haven't been uploaded
again to avoid unnecessary floating patches.
The previous updated series is available at: [3]
But given that, next week I plan to float a separate patch
series, containing the initial patches from the subcommand porting
series (till deinit), which IMO, are ready for maintainer's

Also, this week's update was one-day late, since I was traveling
on the previous day. But a prior idea about this was given to the

PLAN FOR WEEK-14 (15 August 2017 to 21 August 2017):

* patches: Float a separate series, till deinit, and ask the maintainer
  for its review.

* add: The main aim of the next week is to resolve the issues with
  the current patch, and get all the tests pass.

* update: it is the last remaining subcommand to be ported. I aim to
  atleast start with this in the following week.

The work till week-13 is pushed on Github and is available at: [4].


                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:
       or Tor2web:

AGPL code for this site: git clone public-inbox