From: Jeff King <peff@peff.net>
To: "erik elfström" <erik.elfstrom@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git clean performance issues
Date: Sat, 4 Apr 2015 16:48:02 -0400 [thread overview]
Message-ID: <20150404204802.GA558@peff.net> (raw)
In-Reply-To: <CAMpP7NZ8OD5or8H11OvuH1nq+qe-btKCsQnhas6+7SRYE1M1Tw@mail.gmail.com>
On Sat, Apr 04, 2015 at 10:39:47PM +0200, erik elfström wrote:
> That looks like the same issue. The "use is_git_directory" approach
> sounds good to me, is that the direction you would prefer? I can try
> to cobble something together although I must warn you I have zero
> previous experience with this code base so a few iterations will
> probably be needed.
Yeah, I think the preferred direction is building a solution in
is_git_directory. Multiple iterations are fine. That's what review is
for. :) See SubmittingPatches for tips, though.
-Peff
next prev parent reply other threads:[~2015-04-04 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 18:32 git clean performance issues erik elfström
2015-04-04 19:55 ` Jeff King
2015-04-04 20:39 ` erik elfström
2015-04-04 20:48 ` Jeff King [this message]
2015-11-13 14:19 ` Andreas Krey
2015-11-13 23:53 ` Jeff King
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=20150404204802.GA558@peff.net \
--to=peff@peff.net \
--cc=erik.elfstrom@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.
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 NNTP newsgroup(s).