From: Junio C Hamano <gitster@pobox.com>
To: skillzero@gmail.com
Cc: git@vger.kernel.org
Subject: Re: git commit <path> scanning entire working tree?
Date: Mon, 16 Feb 2009 23:12:50 -0800 [thread overview]
Message-ID: <7vvdr98rkd.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <2729632a0902161937o4ac3a1aeg143dda509ba5e384@mail.gmail.com> (skillzero@gmail.com's message of "Mon, 16 Feb 2009 19:37:57 -0800")
skillzero@gmail.com writes:
> ... However, it would
> eliminate information (changed/untracked files outside that path), if
> people are relying on that.
People do rely on that information. Why else we would spend cycles to show
them?
There is a precedence to allow a configuration variable to skip various
computation to help slow systems, e.g. 6c2ce04 (Add argument 'no'
commit/status option -u|--untracked-files, 2008-06-05).
next prev parent reply other threads:[~2009-02-17 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 22:58 git commit <path> scanning entire working tree? skillzero
2009-02-17 0:28 ` Junio C Hamano
2009-02-17 2:57 ` Boyd Stephen Smith Jr.
2009-02-17 3:37 ` skillzero
2009-02-17 5:50 ` Boyd Stephen Smith Jr.
2009-02-17 7:12 ` Junio C Hamano [this message]
2009-02-18 2:25 ` skillzero
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=7vvdr98rkd.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=skillzero@gmail.com \
/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).