Proposal: jcheck restrict addition of subrepo files
mark.reinhold at oracle.com
mark.reinhold at oracle.com
Thu May 16 08:47:37 PDT 2013
2013/5/13 20:53 -0700, chris.hegarty at oracle.com:
> Recently I ran into an issue in a staging forest where a developer, when
> working on a partial forest, accidentally created a directory structure
> in a repository that conflicted with that of one of the sub/inner forest
> repositories.
>
> ...
>
> I've prototyped a very limited solution whereby a repo, through its
> jcheck conf, can define what inner|sub|containing repos are part of its
> forest. jcheck can then trivially prevent files being added that would
> conflict with this.
The incident to which you refer involved the creation of a directory
named jdk/test/closed, which conflicts with an Oracle-internal sub-repo
of closed regression tests. It wouldn't be appropriate for a .jcheck/conf
file in an open repo to refer to a private repo, so I don't think this is
the right approach.
I'm not convinced that it's worth trying to prevent this sort of mistake
is in jcheck. As far as I know it's happened only a few times over the
last seven years.
- Mark
More information about the hg-tools-dev
mailing list