Re: git commit <path> scanning entire working tree?

From: Boyd Stephen Smith Jr. <bss@iguanasuicide.net>
Date: Feb 17, 2009, 05:50 UTC
Message-ID: <200902162350.50946.bss@iguanasuicide.net>
In-Reply-To: <2729632a0902161937o4ac3a1aeg143dda509ba5e384@mail.gmail.com>

On Monday 16 February 2009 21:37:57 you wrote:

Show 11 quoted lines

> On Mon, Feb 16, 2009 at 4:28 PM, Junio C Hamano <gitster@pobox.com> wrote:
> > The template lists "Changes to be committed", but
> > also "Changed but not updated" and "Untracked files".  You cannot
> > generate the latter two lists without checking with your work tree.
>
> It seems like it shouldn't scan/show things outside of the path. If
> I've specified a path on the command line, I most likely only care
> about things in that path. I think it would make committing specific
> paths much faster when you have a large tree. However, it would
> eliminate information (changed/untracked files outside that path), if
> people are relying on that.

Patches reviewed (and possibly accepted) here.

-- 
Boyd Stephen Smith Jr.                   ,= ,-_-. =.
bss@iguanasuicide.net                   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy         `-'(. .)`-'
http://iguanasuicide.net/                    \_/