[] > > If we had such a term in Documentation/glossary-contents.txt, we > could even say > > Add contents of all paths to the index by freshly applying > the "clean" process, even to the ones Git may think are > unmodified in the working tree since they were added the > last time (based on the file timestamps etc.). This is > often useful after updating settings like `core.autocrlf` in > the `.git/config` file and the `text` attributes in the > `.gitattributes` file to correct the index entries that > records lines with CRLF to use LF instead, or changing what > the `clean` filter does. This option implies `-u`. > > The point is to express that the CRLF/LF is a consequence (even > though it may be the most prominent one from end-users' point of > view) of a larger processing. Here is a somwhat shorter description: Apply the "clean" process freshly to all tracked files. This is useful after changing `core.autocrlf` or the `text` attributes in the `.gitattributes` file because Git may not consider these files as changed. Correct the files that had been commited with CRLF, they will from now on have LF instead. Re-run what the `clean` filter does. This option implies `-u`. > > > [snip the TC. Adding line endings is good) > > What is TC in this context? Sorry for confusion: TC means test case.
