On Sun, Oct 19, 2014 at 03:11:33PM +0200, Stephan Beal wrote: > On Sun, Oct 19, 2014 at 2:55 PM, Martin Gagnon <eme...@gmail.com> wrote: > > A possibility could be to only consider the argument as ?FILE? in the > following cases: > A A A A - starting by "./" > A A A A - starting by "/"A A (when using absolute path) > A A A A - when it's "." (for current directory" > > There's nothing in the tag spec prohibiting such tags. e.g. here are tags > starting with "./" and "/":
Oups, I didn't realize that. I propose that because Richard suggest to use "./" to explicitly specify a file/directory on a previous message on this thread. > > http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/info/70feee81d9177f2b5267b63f9a0578103366a625 > > http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/info/7c90c430e812682e444c903e01beec5b8ddc93bb > Fossil applies them fine here: > > http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/info/10f613f8058a657b128f32a1b447ed2e98323561 > Why build complicated heuristics when simply using a flag avoids the > problem altogether? Personally, I think it make more sense to specify ?CHECKINS? and ?WHEN? with a switch and have only the dir/file as argument, like majority or commands. Anyway, when using timeline for the whole repo, most of the time it is used without arguments at all. But it's probably not a good idea because of backward compatibility issue. But if the switch is the only solution, go for it (may be something else than -f). I think backward compatibility is very important too. Regards -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
