On Tue, 08 Jan, Stephan Beal wrote: > On Tue, Jan 8, 2013 at 3:49 PM, Stefan Bellon <sbel...@sbellon.de> > wrote: > > > Is subversion equally frowned upon? If not, what about: > > > > fossil diff --from PREV --to HEAD myfile.c > > > > That would be too easy ;). Yes, it covers the most common case, but it > would be much more interesting to be able to say "go back N > versions", as such a feature implies the "prev" behaviour as well.
fossil diff --from -5 --to -3 myfile.c it is, then. ;-) -0 (or 0) being the current and positive (non-zero) values making no sense (except when being run from inside the time machine shell). > > The question is whether PREV and HEAD (and perhaps other symbolic > > names) should be bound to one branch (i.e. the one of the current > > checked out tree) or whether it should be global and possibly cross > > branches. > > That's a good point. My gut feeling is that the currently-checked-out > branch "should" be used, defaulting to trunk if there is no checkout > (that said, i think we once had a thread where the user had removed > or renamed his trunk branch to something else). Or maybe a syntax like > branch_name:symbolic_name (which of course only works as long as > nobody uses ':' in their branch names). No need for a new syntax (and a very non-fossil one), I think. "fossil diff" already has the option --branch. Currently it is mutually exclusive with --from and --to (because the revision hashes already specify the branch), but that could be used to specify another branch than the current one when using --from and --to with symbolic (or commit-relative) names. Greetings, Stefan -- Stefan Bellon _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
