From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2nd try] runstatus: do not recurse into subdirectories if not needed
Date: Wed, 27 Sep 2006 21:40:50 -0700 [thread overview]
Message-ID: <7v64f861t9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0609280240060.14200@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Thu, 28 Sep 2006 02:44:30 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> This speeds up the case when you run git-status, having an untracked
> subdirectory containing huge amounts of files.
>
> Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
>
> ---
>
> On Thu, 28 Sep 2006, Johannes Schindelin wrote:
>
> Okay, so no more dir_is_empty(). Instead, read_directory_recursive()
> gets a flag. With this flag, "check_only", it exits as soon as it
> found valid entries, but does not add any. Way easier.
Yeah, the logic is a lot easier to follow.
prev parent reply other threads:[~2006-09-28 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 11:16 [PATCH] runstatus: do not recurse into subdirectories if not needed Johannes Schindelin
2006-09-28 0:09 ` Junio C Hamano
2006-09-28 0:26 ` Johannes Schindelin
2006-09-28 0:44 ` [PATCH 2nd try] " Johannes Schindelin
2006-09-28 4:40 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v64f861t9.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox