|
|
| Re: assume unchanged [message #1819047 is a reply to message #577060] |
Mon, 06 January 2020 10:03   |
|
I'm necro-ing this since I just did the exact same manipulation (misclicked in the "git staging" view so a file was flagged as "assume unchanged").
I believe it is extremely dangerous to leave such a command that readily available in the user interface of EGit, or there should at least be a confirmation dialog. Once the user has clicked on it, there is no UI that tells him "which" file has been flagged, or that a file was flagged in the first place. There is no UI to undo that change either. The command line will not show the file in either git status or git diff, so there is no readily available way to determine what has happened for the regular git user.
To make matters worse, the command from Clint above will not work on windows (bash: /mingw64/bin/git: Argument list too long). The user has to dig into the documentation of cgit to understand what that "assume unchanged" has done, and how to actually undo it.
For people who might make the same mistake in the future, you have to open a git terminal and use the following:
$ git ls-files -v|grep '^h'
This will list the files on which the "assume unchanged" flag is set. Then, on each of these files:
$ git update-index --no-assume-unchanged <FILE>
Laurent
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04068 seconds
] 
Search
Help
Register
Login
Home
