[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: How to track history of personal changes in a repository?
From:       Philip Oakley <philipoakley () iee ! email>
Date:       2019-08-31 13:32:28
Message-ID: 2737a9f3-769d-5dc7-ca4e-ef4dbdde70f6 () iee ! email
[Download RAW message or body]

Hi Elijah, Matt

On 30/08/2019 16:21, Elijah Newren wrote:
> * If the changes are to files that are tracked, AND you aren't making
> changes to those same files that do need to be committed and pushed,
> use the assume-unchanged bit (see git-update-index(1)).
Not sure I parsed that well but...

The `assume-unchanged bit` is commonly miss-construed as a promise by 
Git that it will ignore changes to the file.

That is incorrect. The bit is a promise by the _user_ that they won't 
change the file, so that, in general Git stops checking for updates to 
the file.
However it will check for updates sometimes, leading to unexpected 
effects if the user has the wrong mental model, thinking that Git would 
ignore their changes...

Philip
[prev in list] [next in list] [prev in thread] [next in thread]