On 2019-06-17, Quentin Rameau <[email protected]> wrote: >> What's the downside to having it checked into the repository? Are >> there any reasons why a user wouldn't want this feature? Personally, I >> want it in every clone of sbase I make, and I imagine most other >> people want this as well. It is annoying to have `git status` scroll >> my changes off the screen due to all the build artifacts. > > Well, personnaly I don't want it, I prefer to have a clear view of the > clone status, hence the “user-side feature”, as in user-specific > preference.
How do you deal with ~250 lines of "Untracked files:" in the `git status` output? If you want to see them, you can always run `git status --ignored`. >> The place for user-specific and repository-specific ignored files is >> .git/info/exclude. But in general, we don't know the location of the >> .git directory, so we'd probably have to use some git command to >> figure out exactly where to put it. > > There's no “we”, that's the user's responsability to figure out where > to put it. There is a "we" if a Makefile rule were to be added, since it needs to create the file at the appropriate location. > What's the rationale for having it duplicated both in the SCM and in the > Makefile then? So that if a utility is added or removed, .gitignore can easily be kept in sync.
