Suppose a person is managing N repositories. Would that person prefer to
maintain the list of files to ignore for every random IDE that anybody
who joins the team might want to use in:
a: One place
b: N places
On 10/22/21 14:40, Matheus Tavares wrote:
Note that "core.excludesFile" and "$GIT_DIR/info/exclude" are still
allowed to be symlinks.
These are settings that are specific to each developer, right?
If I have N repositories with M developers and I need to add a new
ignore pattern that's either and O(M) or an O(N) job, neither of which
is significantly better than the other and both of which suck compared
to the O(1) functionality that we had before when we could put the list
on a shared submodule.
