From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Andy Parkins <andyparkins@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>, git@vger.kernel.org
Subject: Re: git-status and git-diff now very slow in project with a submodule
Date: Fri, 21 May 2010 14:36:14 +0200 [thread overview]
Message-ID: <AANLkTineTiY0blcQlTRWl-1Q-be6J-EOll2DMReKcUOF@mail.gmail.com> (raw)
In-Reply-To: <201005201901.49853.andyparkins@gmail.com>
On Thu, May 20, 2010 at 8:01 PM, Andy Parkins <andyparkins@gmail.com> wrote:
> On Thursday 20 May 2010 18:49:41 Jens Lehmann wrote:
>> Am 20.05.2010 19:45, schrieb Andy Parkins:
>> > (Most of my
>> > personal use of submodule is embedding large projects that I want to be
>> > able to guarantee are at a particular version, but I don't really
>> > change them)
>>
>> But to guarantee they are at a particular version they have to be checked
>> for local modifications (no matter if they happened accidentally or on
>> purpose), no?
>
> A valid point.
>
> Surely though in my own .git/config I can be allowed to tell git that I
> don't care about that risk?
>
> I've got a top level module that used to diff/status instantly; now git
> scans an entire Linux kernel checkout and an entire ffmpeg checkout.
> Painful. I fully accept that it was my own choice to arrange my repository
> in this way, but in my defence, it was fine last week :-)
Sounds similar to the old "slow lstat" stuff. How about setting
assume-unchanged bit on submodules? I don't know if it works. If it
does not, maybe we could reuse the bit to ignore changes in
submodules.
--
Duy
next prev parent reply other threads:[~2010-05-21 12:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 10:01 git-status and git-diff now very slow in project with a submodule Andy Parkins
2010-05-20 10:10 ` Stefan Naewe
2010-05-20 11:37 ` Andy Parkins
2010-05-20 15:52 ` Michael J Gruber
2010-05-20 17:45 ` Andy Parkins
2010-05-20 17:49 ` Jens Lehmann
2010-05-20 18:01 ` Andy Parkins
2010-05-21 12:36 ` Nguyen Thai Ngoc Duy [this message]
2010-05-20 13:28 ` Junio C Hamano
2010-05-20 17:17 ` Andy Parkins
2010-05-20 22:59 ` Junio C Hamano
2010-05-21 12:05 ` Jens Lehmann
2010-05-21 12:52 ` Leo Razoumov
2010-05-21 17:54 ` Andreas Schwab
2010-05-22 12:05 ` Jens Lehmann
2010-05-22 12:08 ` Jens Lehmann
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=AANLkTineTiY0blcQlTRWl-1Q-be6J-EOll2DMReKcUOF@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=andyparkins@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).