From: Johannes Sixt <j.sixt@viscovery.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "Gaer\, A." <Andreas.Gaer@baslerweb.com>, git@vger.kernel.org
Subject: Re: git performance after directory copy
Date: Mon, 20 Sep 2010 13:48:16 +0200 [thread overview]
Message-ID: <4C974A00.8030905@viscovery.net> (raw)
In-Reply-To: <vpq62y0hh63.fsf@bauges.imag.fr>
Am 9/20/2010 11:56, schrieb Matthieu Moy:
> But I'm surprised that the next "git status" are still slow. Other
> people may get a better explanation, but this very much looks like a
> bug.
Most likely, Andreas works with 1.7.1. From the release notes of 1.7.1.1:
* "git status" stopped refreshing the index by mistake in 1.7.1.
-- Hannes
next prev parent reply other threads:[~2010-09-20 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 9:20 git performance after directory copy Gaer, A.
2010-09-20 9:45 ` Michael J Gruber
2010-09-20 9:56 ` Matthieu Moy
2010-09-20 10:54 ` Michael J Gruber
2010-09-20 11:37 ` AW: " Gaer, A.
2010-09-20 11:48 ` Johannes Sixt [this message]
2010-09-20 11:53 ` Gaer, A.
2010-09-20 13:57 ` Matthieu Moy
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=4C974A00.8030905@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Andreas.Gaer@baslerweb.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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).