Thanks, will apply to 'maint' to be included in v1.5.0.4 (and
also in 'master' to be in v1.5.1).
We should add tests whenever we found this kind of breakage.
For core.sharedrepository, we would want to have something like
this:
(1) Initialize a repository
(2) set core.sharedrepository
(3) set umask to 077
(4) perform various git operations in the repository
(5) "find .git" to see if there is anything unreadable by group
members; if you find any, you found a bug.
That is the "feature" test -- check if a feature works as
intended.
At the same time, we need to have a corresponding "regression"
test to make sure that a feature does not overstep its boundary
and affect cases where it is not enabled:
(1) Initialize a repository
(2) unset core.sharedrepository
(3) set umask to 077
(4) perform various git operations in the repository
(5) "find .git" to see if there is anything readable by group
members; if you find any, you found a bug.
We would need such "regression" tests for existing tests too,
but that is a separate issue.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html