All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-status and git-diff now very slow in project with a submodule
Date: Thu, 20 May 2010 12:37:39 +0100	[thread overview]
Message-ID: <ht36u4$lo4$1@dough.gmane.org> (raw)
In-Reply-To: 4BF50A92.3060209@atlas-elektronik.com

Stefan Naewe wrote:

>> circumstances it is exactly right; however, I'd like to be able to turn
>> off dirty
>> detection in submodules.  Is this already possible, and I've just missed
>> the configuration option?
> 
> Maybe:
> 
>    git config status.submodulesummary false

Hey! Thanks for the reply. Exactly the right option... except it doesn't work :-(

$ git --version
git version 1.7.1
$ git config status.submodulesummary
false
$ git status -uno
# On branch master
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#   (commit or discard the untracked or modified content in submodules)
#
#       modified:   ffmpeg (modified content)
#
no changes added to commit (use "git add" and/or "git commit -a")




Andy

-- 
Dr Andy Parkins
andyparkins@gmail.com

  reply	other threads:[~2010-05-20 11:37 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 [this message]
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
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='ht36u4$lo4$1@dough.gmane.org' \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.