Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ls-files: avoid the verb "deprecate" for individual options
When e750951 (ls-files: guide folks to --exclude-standard over other --exclude* options, 2023-01-13) updated the documentation to give greater visibility to the `--exclude-standard` option, it marked the `--exclude-per-directory` option as "deprecated". While it is technically correct that being deprecated does not necessarily mean it is planned to be removed later, it seems to cause confusion to readers, especially when we merely mean The option Y can be used to achieve the same thing as the option X much simpler. To those of you who aren't familiar with either X or Y, we would recommend to use Y when appropriate. This is especially true for `--exclude-standard` vs the combination of more granular `--exclude-from` and `--exclude-per-directory` options. It is true that one common combination of the granular options can be obtained by just giving the former, but that does not necessarily mean a more granular control is not necessary. State the reason why we recommend readers `--exclude-standard` in the description of `--exclude-per-directory`, instead of saying that the option is deprecated. Also, spell out the recipe to emulate what `--exclude-standard` does, so that the users can give it minute tweaks (like "do the same as Git Porcelain, except I do not want to read the global exclusion file from core.excludes"). Signed-off-by: Junio C Hamano <[email protected]>
- Loading branch information