On Mon, Jul 22, 2013 at 6:02 PM, Jacek Cała <jacek.c...@gmail.com> wrote:
> Sorry for not being precise enough. You don't need to change the central > repo. In fact you don't change any repo at all. Only during cloning you > create a new 'seed' ticket number. Each repository has its own, ticket > number prefix, either '1' if it is created or '...n.n.1' if it is cloned. > When you say "repo" do you mean each clone, or each "central" repo? Together with this 'seed' each repo has it's last_ticket_number variable > (initalized with 1) which is a simple integer added to the seed and > incremented on the 'create ticket' operation. I was to quick to say about > dots only, so the last_ticket_number is added to the seed with, let say, a > dash. Then, a ticket number is constructed as '<seed>-<last_ticket_number>'. > Those would need to be purely local, correct? > Cloning creates a repository tree: > 1 > 1.1 > 1.2 > 1.3 > 1.2.1 > etc. > In the clone or in the central one? > whereas creating tickets adds an internal ticket number (independent for > each repo) and so you can have: > 1-1, 1-2, 1-3 > 1.1-1, 1.1-2 > 1.2.1-1, 1.2.1-2,... > > Is this clearer? > i am assuming by "each repo" you mean "each clone" (which is also "each repo"). If that is the case, i can conceive of this working strictly locally, but i still don't see how it can possibly scale if those numbers propagate in any way. If i clone the repo 100 times, do i end up with 1.1 ... 1.100 ? What if a malicious person clones my repo in a loop a million times? If the numbers are local, not a problem, but if they propagate then that is an attack vector. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
