git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* [GSOC update] Week 1
  2016-04-23 20:10 GSoC Project Selected | Incremental Rewrite of git bisect Pranit Bauva
@ 2016-05-08 11:27 ` Pranit Bauva
  0 siblings, 0 replies; 2+ messages in thread
From: Pranit Bauva @ 2016-05-08 11:27 UTC (permalink / raw)
  To: git; +Cc: christian.couder, chriscool, larsxschneider, Pranit Bauva

My public git.git is available here[1]. I regularly keep pushing my work so
anyone interested can track me there. Feel free to participate in the
discussions going on PRs with my mentors. Your comments are valuable.

The things I was able to do:

 * Finish off with my micro project[2] about adding a config variable for
   git-commit. There is still a little discussion going on about whether
   verbose should be retired and instead "commit.showDiff" should be used.
   Junio also made a little change to squash it with my patch to make the
   patch look more clearer to digest. Its difficult that this will be included
   in the release of 2.8.3

 * I converted the function check_term_format()[3] from shell to C as a
   subcommand. Faced some difficulty but was greatly helped by Christian
   Couder.

 * I converted the function bisect_log()[4] in a branch from the previous
   check-term-format branch as a subcommand. I was waiting for the first patch
   to get queued on maintainer's git.git repo so as to rebase it there and
   then send the patch.

 * I converted the function write_terms()[5] in a branch from the previous
   bisect-log branch as a subcommand and I removed check-term-format subcommand.
   I was waiting for the bisect-log patch to get queued on maintainer's git.git
   repo so as to rebase it there and send send the patch

 * I am currently introducing subcommands and calling them from git-bisect.sh .
   Eric Sunshine had proposed another top bottom approach wherein I first
   implement a skeleton and redirect it to git-bisect.sh so that the test
   suite is still passing. This method was used by Paul Tan in his last year
   GSoC project. Commit ids for reference, e1ea69fa4e and 73c2779f4 .

 * I ignored it and sent another revision of the series to which Junio wasn't
   quite enthusiastic over my reasoning for using subcommand approach. So
   I wrote an email[6] explaining how using subcommand way is beneficial to
   me, reviewers/testers, and my mentors.

 * I am currently waiting for that discussion to come to a conclusion. Till
   then I have paused on a bit.

 * I am now reading on the API part and planning how will I go about with the
   future functions. The functions I have converted till now were quite simple
   ones and the main difficulty lies ahead!

 * Anywhich ways I think this week was quite productive and if I follow this
   speed then the project is in a good shape to be completed well in time.

 * On a lighter note: I will be on a short vacation from 16th May to 19th May.
   So I will be unavailable till that time.

[1]: https://github.com/pranitbauva1997/git
[2]: http://thread.gmane.org/gmane.comp.version-control.git/293635
[3]: https://github.com/pranitbauva1997/git/pull/1
[4]: https://github.com/pranitbauva1997/git/pull/2
[5]: https://github.com/pranitbauva1997/git/pull/3
[6]: http://article.gmane.org/gmane.comp.version-control.git/293909

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [GSoC] Update: Week 1
@ 2017-05-22 17:52 Prathamesh Chavan
  0 siblings, 0 replies; 2+ messages in thread
From: Prathamesh Chavan @ 2017-05-22 17:52 UTC (permalink / raw)
  To: git; +Cc: Stefan Beller, Christian Couder

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:

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.



[1]: https://docs.google.com/document/d/1krxVLooWl--75Pot3dazhfygR3wCUUWZWzTXtK1L-xU/
[2]: https://public-inbox.org/git/20170521125814.26255-1-pc44800@gmail.com/
[3]: https://public-inbox.org/git/20170521125814.26255-2-pc44800@gmail.com/
[4]: https://public-inbox.org/git/20170521122711.22021-1-pc44800@gmail.com/
[5]: https://public-inbox.org/git/20170521122711.22021-2-pc44800@gmail.com/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-05-22 17:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-22 17:52 [GSoC] Update: Week 1 Prathamesh Chavan
  -- strict thread matches above, loose matches on Subject: below --
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

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).