[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Don't complain about changed file when it hasn't changed
From: |
Andreas Schwab |
Subject: |
Re: Don't complain about changed file when it hasn't changed |
Date: |
Tue, 30 Aug 2016 09:55:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
On Aug 30 2016, Stefan Monnier <address@hidden> wrote:
>> I don't understand why Git touches files it doesn't need to change.
>> It can (and does, AFAIK) compute the checksum of a file to know
>> whether it changed.
>
> Usually it changes them then reverts them.
> E.g.:
>
> git stash
> git pull
> git stash pop
>
> all the files modified locally but not in the pulled change will have
> a new timestamp but the same old contents. Since these are separate Git
> invocations, I don't think it would be correct for Git to reset the
> timestamp to some earlier value.
It wouldn't be able to do that anyway, since there is no state recording
the earlier values.
Andreas.
--
Andreas Schwab, SUSE Labs, address@hidden
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
- Re: Don't complain about changed file when it hasn't changed, (continued)