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:

> The default should be tuned for users who perform manual editing
> with status checks.  And power users like yourself who run "bulk
> touch indiscriminately but modify only some" scripts should
> learn to run git-status (or "update-index --refresh") after such
> operation.  Swapping the defaults to optimize for the abnormal
> case is madness.

I fully agree that git should be optimized for the common case. But
even for the common case, I also find the feature strange. You didn't
answer that part of my message, but I still fail to see a rationale
for making "git-diff; git-status" different from "git-status; git-diff".

IOW, why should people running git-status before git-diff not get a
reminder if you think people running git-diff without or before
git-status should get it?

-- 
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