-- Join WANdisco's free daily demo sessions on Scaling Subversion for the Enterprise <http://www.wandisco.com/training/webinars>
----- Original Message ----- > From: Peter Samuelson <pe...@p12n.org> > To: dev@subversion.apache.org > Cc: Julian Foad <julianf...@btopenworld.com>; Patrick Sawyer > <patrick.saw...@wandisco.com>; Support Team <support.t...@wandisco.com> > Sent: Friday, 23 August 2013, 18:58 > Subject: Re: Provide a svn log -v with the option to filter out changeset's > > > [Julian Foad] >> svn log TARGET [SUBTREE...] >> --diff // diff of TARGET [SUBTREE...] >> --diff-all // diff of whole commit >> --show-paths // changed-paths for TARGET [SUBTREE...] >> --show-all-paths // changed-paths for whole commit; alias -v >> -v/--verbose // alias for '--show-all-paths' > > +1, except I'd condense --diff-all and --show-all-paths to a single > additional option named, I dunno, --full-revision. </bikeshed> My latest thought in that area is like I listed above except omitting the --diff-all option entirely -- after all, nobody has requested it and it doesn't seem especially useful to me. Obviously we need the --show-all-paths option for back-compat. (If your suggestion of '--full-revision' meant 'show all paths and show all diffs', then that would not be suitable for back-compat, would it, because what we need is show all paths but no diffs.) - Julian >> This meaning of '--diff' is the same as today when subtrees are not >> specified, different from today when subtrees are specified. (I'd >> argue this is a desirable change.) > > I agree about wanting to change the default meaning of --diff. > Whether we can get away with such an interface change, I'm not sure. > >> Thus, I think it makes sense to implement --depth for the main log >> filtering, not just for the diff. > > +1 again. Final thought: --depth plus --full-revision doesn't really > make sense, does it? If so, what would it do? > > Peter >
