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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 16 February 2009 21:37:57 you wrote:
> On Mon, Feb 16, 2009 at 4:28 PM, Junio C Hamano <gitster@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxx                   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy         `-'(. .)`-'
http://iguanasuicide.net/                    \_/

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux