Hi, Chet. I'm a beginner with Bash and recently stumbled upon the Bash code repository (specifically the 'devel' branch). I noticed that almost every commit includes thousands of lines of changes.
Out of curiosity, I randomly clicked on one of the commits (e.g., <https://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=772e7e760e8a098e4d8dee21cf11090be4757918>). I found that the majority of the changes were to documentation, such as the `doc/bash.0` file, which had 4999 lines modified. While I'm not very familiar with the process of automatically generating documentation, I can still infer that the `doc/bash.0` file is an output produced by processing `doc/bash.info` with some program. I believe these output files should be added to `.gitignore` and generated during the `make` process. Otherwise, they will severely pollute the commit history, making it much harder for future maintainers to understand and manage the repository. -- shynur
