mailing list mirror (one of many)
 help / Atom feed
From: Prathamesh Chavan <>
To: git <>
Cc: Stefan Beller <>,
	Christian Couder <>
Subject: [GSoC] Update: Week 1
Date: Mon, 22 May 2017 23:22:59 +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 planned for the first week, I continued working on completing the porting
of submodule subcommand foreach. As suggested in the previous patches, some
additional changes we made to the patch and an updated version of the patch
is posted on the mailing list.[2][3]

Also, porting of submodule subcommand status from shell to C was carried out
in this week. For this purpose, first the function set_name_rev was ported
from shell to C, and then the subcommand. A complete ported version, which
passes all the tests is posted on the mailing list for reviews.[4][5]

PLAN FOR WEEK-2 (23 May 2017 to 29 may 2017):

In this week, I plan to port submodule subcommand sync from shell to C and
post a version of the ported function on the mailing list asap.

Also, I'll get started with porting the submodule subcommand summary in this
week itself and will try my best to port this as well in this week.

Along with this, I'll continue improvising the present patches, which are
currently on the mailing list for reviews.


             reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23 20:10 GSoC Project Selected | Incremental Rewrite of git bisect Pranit Bauva
2016-05-08 11:27 ` [GSOC update] Week 1 Pranit Bauva
2017-05-22 17:52 Prathamesh Chavan [this message]

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