On Sun, Oct 19, 2014 at 10:14:21AM +0200, Stefan Bellon wrote: <snip> > > One could check whether it exists in the file system and one could > check whether exists as tag/branch and decide to use the one that > exists. However, if "trunk" exists both, as branch and as > file/directory, then a priority decision has to be done anyway and this > seems strange as you cannot rely on the behaviour when writing generic > fossil interaction scripts.
Actually, it's impossible right now with version from trunk to just specify a checkin without also specifying the ?WHEN? argument. Example: $ fossil timeline trunk Fail right now.. <snip> > But why not just use some switch to indicate that the following > argument is a file/directory rather than a branch/tag/...? > > fossil timeline -f README.txt > > This way the previous behaviour would be completely unaltered without > any compatibility issues, but the new way is possible as well by just > adding -f (or whatever) to the command. Alternatively one could > introduce a new command "ftimeline", but I think a switch would be > sufficient. Look at latest checkin on the cmdline-timeline-enhancement branch. http://www.fossil-scm.org/index.html/info/1e870e1e06c202a855afcd364826b35dbdb6d8ef File or directory is now specified with -p or --path, since -f was already used (deprecated --showfiles|-f option. I've also restore the previous timeline argument parsing so now you can just type: $ fossil timeline trunk Like before. Please test if it's ok, so it can be merge on trunk. 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
