[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Easier to read multi-line properties in proplist and propget

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Thu, 14 Aug 2008 15:33:51 +0100

On Thu, 2008-08-14 at 10:21 -0400, C. Michael Pilato wrote:
> Ivan Zhakov wrote:
> > 2008/8/14 Julian Foad <julianfoad_at_btopenworld.com>:
> >> I would like to know people's views on whether either or both of these
> >> changes are a good idea, backward compatibility concerns, whether these
> >> changes should be optional (like with "propget --verbose") or the
> >> default, etc.
> >>
> > I like new format and --verbose option for proplist.
>
> (You mean 'propget' -- proplist already has a --verbose option.)
>
> Julian, does your proposal/patch continue to handle the --strict option to
> propget correctly? --strict causes byte-for-byte spewing of the property
> values, without associated filenames, character transcoding, etc.

Yes, it does. It doesn't allow --verbose to be specified in conjunction
with --strict (nor with --xml nor with --revprop).

> (Actually, come to think of it, --strict *should* today raise an error if
> used with more than one target, but it doesn't. It just concatenates the
> multiple property values in the output stream.)

Yes, I've always thought that was almost useless. I'm not touching it
here though.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-14 16:34:12 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.