You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Patrick Sawyer <pa...@wandisco.com> on 2013/09/03 14:21:38 UTC

Re: Provide a svn log -v with the option to filter out changeset's

Thanks all.

So it appears that every one agrees this is a valid improvement. Has this
been raised into your issue tracker and do we have a reference number for
this improvement? Thanks


Regards


Patrick Sawyer | *Deployment Coordinator  *

*
*

WANdisco // *Non-Stop Data*

t. +44 (0)114 303 02 58
h. +44 (0)114 303 99 85 ext.612
e. patrick.sawyer@wandisco.com




On Sat, Aug 24, 2013 at 9:47 AM, Julian Foad <ju...@btopenworld.com>wrote:

> Peter Samuelson wrote:
> >>> +1, except I'd condense --diff-all and --show-all-paths to a single
> >>> additional option named, I dunno, --full-revision. </bikeshed>
> >
> > [Julian Foad]
> >> 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.
> >
> > Well, "nobody has requested it" is meaningless, since they already have
> > it today, with '--diff'.
>
> Actually no: --diff currently shows the diff of the subtree at the
> specified main target path only, not of the whole revision.
>
> > But... either way.  I note that it's also
> > what 'git diff' does (annoying, but 'git diff .' is a simple
> > workaround).
> >
> >> 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.)
> >
> > No, I meant '--diff --full-revision' or '--show-paths --full-revision'.
> > In fact I'd shorten --show-paths to --paths, to match --diff.  And
> > --full-revision could perhaps be shorter as well.
>
> That makes sense, as one reasonable option.
>
> So we have plenty of interest in this, and ideas for the UI.  Do we have
> anybody who might step up to implement it?
>
> - Julian
>
>

-- 
Listed on the London Stock Exchange: WAND<http://www.bloomberg.com/quote/WAND:LN>
*
*
*Register now for* Subversion & Git Live October 2013<http://www.wandisco.com/subversion-live-2013>
* **in** **Boston / San Francisco /** London*

THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE 
PRIVILEGED.  If this message was misdirected, WANdisco, Inc. and its 
subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. 
 If you are not the intended recipient, please notify us immediately and 
destroy the message without disclosing its contents to anyone.  Any 
distribution, use or copying of this e-mail or the information it contains 
by other than an intended recipient is unauthorized.  The views and 
opinions expressed in this e-mail message are the author's own and may not 
reflect the views and opinions of WANdisco, unless the author is authorized 
by WANdisco to express such views or opinions on its behalf.  All email 
sent to or from this address is subject to electronic storage and review by 
WANdisco.  Although WANdisco operates anti-virus programs, it does not 
accept responsibility for any damage whatsoever caused by viruses being 
passed.


Re: Provide a svn log -v with the option to filter out changeset's

Posted by Julian Foad <ju...@btopenworld.com>.
Patrick Sawyer wrote:
> Thanks all.
> 
> So it appears that every one agrees this is a valid improvement. Has
> this been raised into your issue tracker and do we have a reference
> number for this improvement? Thanks

Hi Patrick.  I've just filed issue #4419, "Restrict changed-paths list in 'log -v' to only the target subtree", for this: <http://subversion.tigris.org/issues/show_bug.cgi?id=4419>.

- Julian


> On Sat, Aug 24, 2013 at 9:47 AM, Julian Foad wrote:
[...]
>> So we have plenty of interest in this, and ideas for the UI.  Do we have
>> anybody who might step up to implement it?