On 5/11/15, Abilio Marques <abili...@gmail.com> wrote: > I recall seeing no way of detecting a "push" to a specific > branch. All I saw were deltas and stuff like that. > > Am I wrong? or is there a way the server could forbid an user to push to > some branches and give an error?
You are correct. The push/pull logic in SQLite knows nothing about branches or check-ins or tags or any other details of the repository. The push/pull logic simply strives to make sure that both repositories have the same set of artifacts. To change Fossil to have the ability to prevent pushes to certain branches, we would have to add knowledge of branches and check-ins to the push/pull logic. Note also that this goes against one of the founding principles of Fossil: that the VCS should implement mechanism not policy. That is to say, details of who should be able to check-in to which branches and whatnot should not be enforced by the VCS. Project policies need to be enforced by some other means. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
