Julian Foad wrote:
> C. Michael Pilato wrote:
>> Julian Foad wrote:
>>> I think I need to tweak the new indented "svn propget" output format.
>>> Some time back (r32484) I changed the output format of "svn proplist -v"
>>> to indent every line of a multi-line property value, to make it
>>> parseable and more readable:
>>> For "svn propget", I made a similar change, but a little differently. In
>>> comparison to v1.5, the new format always shows the file name, always
>>> shows the property name, and indents the value, but I chose to make this
>>> new format happen only with "-v/--verbose", feeling that tools might be
>>> more commonly parsing the output (at least when it is parseable, such as
>>> when requesting just one property from one target). The command did not
>>> use "-v" before.
>> I actually misread the finer details of your mail, and started to propose an
>> alternative. In pre-send-the-mail review, though, I realized my mistake --
>> I had just proposed exactly the state of trunk today. Apparently, my mind
>> is saying "Leave it as it is."
> So you don't mind "-v" being introduced to "propget" to mean "use the
> new format", but "proplist" using the new format by default (and "-v"
> already being used for "show the values")?
I don't mind propget's default changing if a) we already did that with
proplist with no public outcry and b) the --strict mode (which is what I
would expect most folks using pget in scripts would be using) continues to
work as it does today.
I don't mind adding -v to enable this for propget if we promise to always
show the paths (because besides being a better format, we actually are being
a little more verbose than before).
And, though it doesn't really apply to this context so much, I actually
don't mind a little snow in the Charlotte area. It's white. It's fluffy.
And it flips my kids' energy knobs to 11. (Whoops. Somebody ran cmpilato
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2009-01-20 15:40:37 CET