From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: vaibhav kurhe <vaibhav.kurhe@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Want to start contributing to git through this task: "Use dir-iterator to avoid explicit recursiv
Date: Tue, 10 Apr 2018 10:41:30 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1804101040090.55@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> (raw)
In-Reply-To: <CAPig+cRNbDBpDn_ku0cXJhzvnrSOkBTztp8tWomePxfXaviotw@mail.gmail.com>
Hi,
On Mon, 9 Apr 2018, Eric Sunshine wrote:
> On Mon, Apr 9, 2018 at 9:51 AM, vaibhav kurhe <vaibhav.kurhe@gmail.com> wrote:
> > 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"
> > 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.
>
> There has been no recent discussion on the mailing list regarding
> this, so it is unlikely that anyone else is working on it.
Indeed.
Please feel free to reach out when you get stuck. If you want to show the
code in progress, may I suggest to publish your topic branch to a public
repository, such as on GitHub?
Ciao,
Johannes
prev parent reply other threads:[~2018-04-10 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 13:51 Want to start contributing to git through this task: "Use dir-iterator to avoid explicit recursiv vaibhav kurhe
2018-04-09 18:05 ` Eric Sunshine
2018-04-10 8:41 ` Johannes Schindelin [this message]
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=nycvar.QRO.7.76.6.1804101040090.55@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
--cc=vaibhav.kurhe@gmail.com \
/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).