On Mon, Apr 14, 2014 at 3:03 PM, Tony Papadimitriou <to...@acm.org> wrote:
> I realize, this in effect is the same as using the DIFF command with > the --BRIEF option, but CHANGES is what one expects to type when looking > for filename differences, rather than content differences, so it seems more > relevant for this operation to be under CHANGES, rather than a special > option of DIFF. > i disagree - "changes" is intended to show local changes vs the current version: [stephan@host:~]$ f help changes Usage: f changes ?OPTIONS? Report on the edit status of all files in the current checkout. ... (That said, i've never ever used 'changes' because i'm too used to 'status', the name CVS/SVN used for this feature.) If you want to see changes against a specific version, it's like you said: [stephan@host:~/cvs/fossil/fossil]$ f diff --from prev --brief CHANGED src/timeline.c CHANGED www/changes.wiki [stephan@host:~/cvs/fossil/fossil]$ f diff --from version-1.28 --brief CHANGED BUILD.txt CHANGED COPYRIGHT-BSD2.txt CHANGED Makefile.Cygwin.in CHANGED Makefile.in CHANGED auto.def CHANGED src/add.c ... -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
