mailing list mirror (one of many)
 help / Atom feed
From: Prathamesh Chavan <>
To: git <>
Cc: Stefan Beller <>,
	Christian Couder <>
Subject: [GSoC] Update: Week 0 (Community Bonding Period)
Date: Tue, 16 May 2017 01:56:37 +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 <>


As proposed, till 15th May I mostly spend my time updating my information
about the codebase.

Along with this, I even spend some time working on the patch:
submodule: port subcommand foreach from shell to C[2]
I even updated my patch by sending v3, and adding a test[3] to
the existing ones. Currently, the patch passes all the test,
except the newly added one.


As proposed, I would be starting to code officially from 16th May
(tomorrow), and hence have plans for working as follows:

Improvise submodule: port subcommand foreach from shell to C patch,
as suggested and also work on getting the newly added test passed.
I have recently received review from Brandon Williams <>
and my mentor Stefan Beller <> which I am really
thankful for, and wish to implement these suggestions as soon as

Adding to this, I am also waiting for the community's review on the
issue regarding the $path variable, which I added along with the
patch[2]. This issue is also highlighted by the new test[3] added.
Any suggestion would be of huge help to work further on getting
all the tests clear.

Along with this, I plan to port submodule subcommand status.
This required first porting of the function set_name_rev from
shell to C, and then later port the subcommand.


                 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