You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ivan Zhakov <ch...@gmail.com> on 2008/08/14 13:19:37 UTC
Re: [PATCH] Easier to read multi-line properties in proplist and propget
2008/8/14 Julian Foad <ju...@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.
--
Ivan Zhakov
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Easier to read multi-line properties in proplist and
propget
Posted by "C. Michael Pilato" <cm...@collab.net>.
Julian Foad wrote:
> On Thu, 2008-08-14 at 10:21 -0400, C. Michael Pilato wrote:
>> (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.
I'll plug that hole myself right now.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: [PATCH] Easier to read multi-line properties in proplist and
propget
Posted by Julian Foad <ju...@btopenworld.com>.
On Thu, 2008-08-14 at 10:21 -0400, C. Michael Pilato wrote:
> Ivan Zhakov wrote:
> > 2008/8/14 Julian Foad <ju...@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@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Easier to read multi-line properties in proplist and
propget
Posted by "C. Michael Pilato" <cm...@collab.net>.
Ivan Zhakov wrote:
> 2008/8/14 Julian Foad <ju...@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.
(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.)
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand