mailing list mirror (one of many)
 help / Atom feed
From: Prathamesh Chavan <>
To: git <>
Cc: Stefan Beller <>,
	Christian Couder <>
Subject: [GSoC] Update: Week 14
Date: Tue, 22 Aug 2017 02:18:48 +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: Although much time was spent by me on trying to debug the
  patch, the attempts made were unsuccessful or were
  rather partially successful (since while fixing one issue,
  they invoked a different one). After getting   suggestions and
  help from mentors for the remaining tests, now there are only
  two tests which the patch is currently failing at.
  The current status of the patch can be viewed at [2].

* update: porting this subcommand is already underway, and
  porting of the functions is_tip_reachable() and
  fetch_in_submodule() as completed.

* patches: a smaller patch series is floated on the mailing list
  for the maintainer's review.

The small patch series which recently was floated is pushed on Github
and is available at [3].

PLAN FOR WEEK-15 (22 August 2017 to 28 August 2017):

* add: One of the main aims of the next week is to resolve the
  the two tests which the current patch fails at.

* patches: will be working on getting the smaller series merged, and
  once its done, will prepare and float the next patch for the
  same purpose. Till then, I aim to stay more active on the mailing
  list as well for responding to the reviews.

Since I am a bit busier the following week (due to college academics),
I will resume porting submodule subcommand 'update' in the following week.


                 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 \ \ \ \ \ \

* 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