git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: vaibhav kurhe <vaibhav.kurhe@gmail.com>
To: git@vger.kernel.org
Subject: Want to start contributing to git through this task: "Use dir-iterator to avoid explicit recursiv
Date: Mon, 9 Apr 2018 19:21:44 +0530	[thread overview]
Message-ID: <CAHKv1qs-cnmcd2pR9iv=Xx1aKnb=SEsCQ7OAjy-4yHhCE_e_dw@mail.gmail.com> (raw)

Hello all,
I am a Git user since last 2 years and now I want to contribute
towards its development.
Yesterday, I had a discussion with Kevin on the IRC channel
#git-devel, where I got this link:-
https://git.github.io/SoC-2018-Microprojects/.
Out of the tasks listed down in above URL, I found this one interesting:-
"Use dir-iterator to avoid explicit recursive directory traversal"
==>
Some places in git use raw API opendir/readdir/closedir to traverse a
directory recursively, which usually involves function recursion. Now
that we have struct dir_iterator (see dir-iterator.h), convert these
to use the dir-iterator to simplify the code. Do only one conversion
per microproject.

I cloned the git repo and browsed through it. I found that in git
clone (buildtin/clone.c), raw directory API readdir() is used
recursively.
So there is a place to change it to use the already available
"dir_iterator" structure.

I just want to know, if anybody is working on this task already.
If not, then I can proceed to work.

Thank you and Regards,
Vaibhav

             reply	other threads:[~2018-04-09 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 13:51 vaibhav kurhe [this message]
2018-04-09 18:05 ` Want to start contributing to git through this task: "Use dir-iterator to avoid explicit recursiv Eric Sunshine
2018-04-10  8:41   ` Johannes Schindelin

Reply instructions:

You may reply publicly 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CAHKv1qs-cnmcd2pR9iv=Xx1aKnb=SEsCQ7OAjy-4yHhCE_e_dw@mail.gmail.com' \
    --to=vaibhav.kurhe@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).