Re: git-diff on touched files: bug or feature?

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

 



Junio C Hamano <gitster@xxxxxxxxx> writes:

> Quite honestly, a script that indiscriminately touches everybody
> but only modifies a few is simply broken.  Think about "make".
> "git diff" reporting many cache-dirty files is simply reminding
> you the brokenness of such a script.

I wouldn't call this "broken", but clearly suboptimal, yes. But for an
occasionnal one-liner (perl -pi -e ... or so), I lose less time
recompiling extra-files than I would writting a cleaner script. "make"
has no way to detect the absence of modification, while git has.

-- 
Matthieu
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[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