On Wed, Aug 21, 2013 at 5:26 PM, Mark Janssen <mpc.jans...@gmail.com> wrote:
> One reason which would make my life easier is when dealing with tickets, > it is much easier to discuss bug 12 (in blessed repo X) instead of ticket > uuid [some 8+ digit number]. When I work with tickets on github I know the > bug ids of tickets I am working on. When working with fossil I always have > to look up the uuid. > But ticket discussions assume non-local use (b/c others need those ticket numbers, too), and that's where sequential numbering flies out the window in a DVCS. i'd LOVE to see it solved, but all the discussions i've read on the topic, and my derived understanding, is that it "cannot be done" in the DVCS model. If someone can suggest an implementation which is neither subject to misuse, exposes no internal data, and is not too terribly intrusive, i will commit to implementing it (as a reward to you guys who are (understandably) sick of hearing me say "it can't be done!" ;). -- ----- 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
