On 13/05/15 16:45, Ramon Ribó wrote:
Hello,
A reasonable solution could be a pre-commit hook, where the script in
TH1 or TCL had access to the branch name of the commit and other
details. As a result, the hook could accept the commit, raise a
warning, ask for confirmation or deny the commit.
This hook would not stop a determined hacker to make a sabotage of the
repository, but would give some control over the distracted programmer.
And in my experience it is much more common to deal with distracted
programmers than with professional saboteurs.
RR
It wouldn't offer much control over a distracted programmer, because
your local repo is always going to be under the full control of the user
on the local machine - no hacking required.
In which case, all you can do is prompt asking are you sure you want to
commit to this branch.
Is that feature really that useful? Maybe someone who thinks it us could
write some code and supply it as a bundle so other's interested can try
it, and see if it truly helps or is a hindrance in practice.
I don't know the fossil codebase, so I don't know what's easiest to do,
whether to add a TH hook, or for the sake of investigative purposes,
just add another setting, which maybe takes a regexp, which is then used
to determine whether or not to prompt.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
