You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Julian Foad <ju...@btopenworld.com> on 2009/01/20 12:31:32 UTC
[RFC] New indented propget/proplist output needs a tweak for v1.6
I think I need to tweak the new indented "svn propget" output format.
BACKGROUND
==========
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:
In v1.5:
[[[
$ svn-1.5.4 proplist -v subversion/tests/cmdline/
Properties on 'subversion/tests/cmdline':
svn:ignore : svn-test-work
httpd-*
.gdb_history
*.pyc
...
]]]
In trunk:
[[[
$ svn proplist -v subversion/tests/cmdline/
Properties on 'subversion/tests/cmdline':
svn:ignore
svn-test-work
httpd-*
.gdb_history
*.pyc
...
]]]
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.
In v1.5, and also in trunk without "-v":
[[[
$ svn-1.5.4 propget svn:ignore subversion/tests/cmdline/
svn-test-work
httpd-*
.gdb_history
*.pyc
...
$ svn-1.5.4 propget -R svn:ignore subversion/tests/cmdline/
subversion/tests/cmdline/svntest - *.pyc
*.o
...
subversion/tests/cmdline - svn-test-work
httpd-*
.gdb_history
*.pyc
...
]]]
In trunk:
[[[
$ svn propget -v svn:ignore subversion/tests/cmdline/
Properties on 'subversion/tests/cmdline':
svn:ignore
svn-test-work
httpd-*
.gdb_history
*.pyc
...
$ svn propget -vR svn:ignore subversion/tests/cmdline/
Properties on 'subversion/tests/cmdline/svntest':
svn:ignore
*.pyc
*.o
...
Properties on 'subversion/tests/cmdline':
svn:ignore
svn-test-work
httpd-*
.gdb_history
*.pyc
...
]]]
The benefit is seen better with recursive or longer listings, especially
with long values like svn:mergeinfo and svn:ignore. (For properties with
short names and short single-line values, the old format looks nicer for
some purposes.)
NOW...
======
I don't like using "-v" to change propget's output format, and part of
the reason I left it like that is so we can get a feel for which we
prefer.
I think we should:
A. Make "propget" print just the plain value with no header when there
is only one target, like it used to, but use the new indented format
when there are multiple targets. Remove the new use of "-v". (Leave
"proplist" as it
If you care, please have a look and a think. Alternatives are:
B. Leave it as it is.
C. Make "propget" use the new indented format always (like "proplist"
does), and so not add the use of the "--verbose" option in that command.
D. Revert the change to "proplist" and go back to its old messy
output, for pure compatibility.
I'll do (A) unless I hear a convincing argument to the contrary.
- Julian
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1037861
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Arfrever Frehtes Taifersar Arahesis <Ar...@GMail.Com>.
2009-01-20 13:31 Julian Foad <ju...@btopenworld.com> napisał(a):
> I think I need to tweak the new indented "svn propget" output format.
>
>
> BACKGROUND
> ==========
>
> 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:
>
> In v1.5:
> [[[
> $ svn-1.5.4 proplist -v subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore : svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> In trunk:
> [[[
> $ svn proplist -v subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> 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.
>
> In v1.5, and also in trunk without "-v":
> [[[
> $ svn-1.5.4 propget svn:ignore subversion/tests/cmdline/
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
>
> $ svn-1.5.4 propget -R svn:ignore subversion/tests/cmdline/
> subversion/tests/cmdline/svntest - *.pyc
> *.o
> ...
> subversion/tests/cmdline - svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> In trunk:
> [[[
> $ svn propget -v svn:ignore subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
>
> $ svn propget -vR svn:ignore subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline/svntest':
> svn:ignore
> *.pyc
> *.o
> ...
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> The benefit is seen better with recursive or longer listings, especially
> with long values like svn:mergeinfo and svn:ignore. (For properties with
> short names and short single-line values, the old format looks nicer for
> some purposes.)
>
>
> NOW...
> ======
>
> I don't like using "-v" to change propget's output format, and part of
> the reason I left it like that is so we can get a feel for which we
> prefer.
>
> I think we should:
>
> A. Make "propget" print just the plain value with no header when there
> is only one target, like it used to, but use the new indented format
> when there are multiple targets. Remove the new use of "-v". (Leave
> "proplist" as it
>
> If you care, please have a look and a think. Alternatives are:
>
> B. Leave it as it is.
>
> C. Make "propget" use the new indented format always (like "proplist"
> does), and so not add the use of the "--verbose" option in that command.
>
> D. Revert the change to "proplist" and go back to its old messy
> output, for pure compatibility.
>
> I'll do (A) unless I hear a convincing argument to the contrary.
+1 for B.
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Julian Foad <ju...@btopenworld.com>.
David Glasser wrote:
> One clarification: The old 'pg', with multiple targets or -R, was not
> actually machine-parsable, right?
Correct, and the new output is machine-parsable.
- Julian
> --dave
>
> On Tue, Jan 20, 2009 at 4:31 AM, Julian Foad <ju...@btopenworld.com> wrote:
> > I think I need to tweak the new indented "svn propget" output format.
> >
> >
> > BACKGROUND
> > ==========
> >
> > 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:
> >
> > In v1.5:
> > [[[
> > $ svn-1.5.4 proplist -v subversion/tests/cmdline/
> > Properties on 'subversion/tests/cmdline':
> > svn:ignore : svn-test-work
> > httpd-*
> > .gdb_history
> > *.pyc
> > ...
> > ]]]
> >
> > In trunk:
> > [[[
> > $ svn proplist -v subversion/tests/cmdline/
> > Properties on 'subversion/tests/cmdline':
> > svn:ignore
> > svn-test-work
> > httpd-*
> > .gdb_history
> > *.pyc
> > ...
> > ]]]
> >
> > 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.
> >
> > In v1.5, and also in trunk without "-v":
> > [[[
> > $ svn-1.5.4 propget svn:ignore subversion/tests/cmdline/
> > svn-test-work
> > httpd-*
> > .gdb_history
> > *.pyc
> > ...
> >
> > $ svn-1.5.4 propget -R svn:ignore subversion/tests/cmdline/
> > subversion/tests/cmdline/svntest - *.pyc
> > *.o
> > ...
> > subversion/tests/cmdline - svn-test-work
> > httpd-*
> > .gdb_history
> > *.pyc
> > ...
> > ]]]
> >
> > In trunk:
> > [[[
> > $ svn propget -v svn:ignore subversion/tests/cmdline/
> > Properties on 'subversion/tests/cmdline':
> > svn:ignore
> > svn-test-work
> > httpd-*
> > .gdb_history
> > *.pyc
> > ...
> >
> > $ svn propget -vR svn:ignore subversion/tests/cmdline/
> > Properties on 'subversion/tests/cmdline/svntest':
> > svn:ignore
> > *.pyc
> > *.o
> > ...
> > Properties on 'subversion/tests/cmdline':
> > svn:ignore
> > svn-test-work
> > httpd-*
> > .gdb_history
> > *.pyc
> > ...
> > ]]]
> >
> > The benefit is seen better with recursive or longer listings, especially
> > with long values like svn:mergeinfo and svn:ignore. (For properties with
> > short names and short single-line values, the old format looks nicer for
> > some purposes.)
> >
> >
> > NOW...
> > ======
> >
> > I don't like using "-v" to change propget's output format, and part of
> > the reason I left it like that is so we can get a feel for which we
> > prefer.
> >
> > I think we should:
> >
> > A. Make "propget" print just the plain value with no header when there
> > is only one target, like it used to, but use the new indented format
> > when there are multiple targets. Remove the new use of "-v". (Leave
> > "proplist" as it
> >
> > If you care, please have a look and a think. Alternatives are:
> >
> > B. Leave it as it is.
> >
> > C. Make "propget" use the new indented format always (like "proplist"
> > does), and so not add the use of the "--verbose" option in that command.
> >
> > D. Revert the change to "proplist" and go back to its old messy
> > output, for pure compatibility.
> >
> > I'll do (A) unless I hear a convincing argument to the contrary.
> >
> > - Julian
> >
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1041159
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by David Glasser <gl...@davidglasser.net>.
One clarification: The old 'pg', with multiple targets or -R, was not
actually machine-parsable, right?
--dave
On Tue, Jan 20, 2009 at 4:31 AM, Julian Foad <ju...@btopenworld.com> wrote:
> I think I need to tweak the new indented "svn propget" output format.
>
>
> BACKGROUND
> ==========
>
> 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:
>
> In v1.5:
> [[[
> $ svn-1.5.4 proplist -v subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore : svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> In trunk:
> [[[
> $ svn proplist -v subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> 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.
>
> In v1.5, and also in trunk without "-v":
> [[[
> $ svn-1.5.4 propget svn:ignore subversion/tests/cmdline/
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
>
> $ svn-1.5.4 propget -R svn:ignore subversion/tests/cmdline/
> subversion/tests/cmdline/svntest - *.pyc
> *.o
> ...
> subversion/tests/cmdline - svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> In trunk:
> [[[
> $ svn propget -v svn:ignore subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
>
> $ svn propget -vR svn:ignore subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline/svntest':
> svn:ignore
> *.pyc
> *.o
> ...
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> The benefit is seen better with recursive or longer listings, especially
> with long values like svn:mergeinfo and svn:ignore. (For properties with
> short names and short single-line values, the old format looks nicer for
> some purposes.)
>
>
> NOW...
> ======
>
> I don't like using "-v" to change propget's output format, and part of
> the reason I left it like that is so we can get a feel for which we
> prefer.
>
> I think we should:
>
> A. Make "propget" print just the plain value with no header when there
> is only one target, like it used to, but use the new indented format
> when there are multiple targets. Remove the new use of "-v". (Leave
> "proplist" as it
>
> If you care, please have a look and a think. Alternatives are:
>
> B. Leave it as it is.
>
> C. Make "propget" use the new indented format always (like "proplist"
> does), and so not add the use of the "--verbose" option in that command.
>
> D. Revert the change to "proplist" and go back to its old messy
> output, for pure compatibility.
>
> I'll do (A) unless I hear a convincing argument to the contrary.
>
> - Julian
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1037861
>
--
glasser@davidglasser.net | langtonlabs.org | flickr.com/photos/glasser/
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Michael Haggerty <mh...@alum.mit.edu>.
Julian Foad wrote:
> As for Mike's comment about "proplist" format having changed with "no
> public outcry", it hasn't been in a release yet...
And, nevertheless, I *did* cry out, in my own tiny voice:
http://subversion.tigris.org/ds/viewMessage.do?dsMessageId=81928&dsForumId=462
Summary: even SVN's own test infrastructure does not work across
"proplist" formats.
Michael
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1041525
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Julian Foad <ju...@btopenworld.com>.
On Tue, 2009-01-20 at 10:01 -0500, Paul Burba wrote:
> On Tue, Jan 20, 2009 at 9:39 AM, Julian Foad <ju...@btopenworld.com> wrote:
> > On Tue, 2009-01-20 at 09:28 -0500, Paul Burba wrote:
> >> On Tue, Jan 20, 2009 at 8:43 AM, C. Michael Pilato <cm...@collab.net> wrote:
> >> >> A. Make "propget" print just the plain value with no header when there
> >> >> is only one target, like it used to, but use the new indented format
> >> >> when there are multiple targets. Remove the new use of "-v". (Leave
> >> >> "proplist" as it
> >> >
> >> > Do you mean "multiple targets" or "multiple targets with the named
> >> > property"? Actually, that's not even so very interesting. I guess I don't
> >> > like the idea that somebody might type:
> >>
> >> This is probably the same question as Mike's, but what would a
> >> recursive propget yield? The same indented output as with multiple
> >> targets right? I'd hate svn pg svn:mergeinfo -vR to return to the
> >> mess it was.
> >
> > I mean whatever the plain (old-style and still default) "propget"
> > currently does,
>
> Ok, but that default style is really tough on the eyes when dealing
> with subtrees and mergeinfo. Run 'svn pg svn:mergeinfo -R' on [...]
Sorry, mis-communication there. I didn't mean a recursive propget would
print the old format, I meant a recursive propget would choose formatted
output instead of value-only output.
So:
A. Make "propget" print just the plain value with no header when there
is only one target, like it used to, but use the new indented format
when there may be multiple results (e.g. with "-R" or multiple
command-line targets). Remove the new use of "-v". (Leave "proplist" as
it is.)
But it looks like nobody particularly wants me to make that change.
As for Mike's comment about "proplist" format having changed with "no
public outcry", it hasn't been in a release yet...
- Julian
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1038292
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Paul Burba <pt...@gmail.com>.
On Tue, Jan 20, 2009 at 9:39 AM, Julian Foad <ju...@btopenworld.com> wrote:
> On Tue, 2009-01-20 at 09:28 -0500, Paul Burba wrote:
>> On Tue, Jan 20, 2009 at 8:43 AM, C. Michael Pilato <cm...@collab.net> wrote:
>> >> A. Make "propget" print just the plain value with no header when there
>> >> is only one target, like it used to, but use the new indented format
>> >> when there are multiple targets. Remove the new use of "-v". (Leave
>> >> "proplist" as it
>> >
>> > Do you mean "multiple targets" or "multiple targets with the named
>> > property"? Actually, that's not even so very interesting. I guess I don't
>> > like the idea that somebody might type:
>>
>> This is probably the same question as Mike's, but what would a
>> recursive propget yield? The same indented output as with multiple
>> targets right? I'd hate svn pg svn:mergeinfo -vR to return to the
>> mess it was.
>
> I mean whatever the plain (old-style and still default) "propget"
> currently does,
Ok, but that default style is really tough on the eyes when dealing
with subtrees and mergeinfo. Run 'svn pg svn:mergeinfo -R' on the
root of the 1.5.x branch to see what I mean. In contrast run 'svn pg
svn:mergeinfo -vR'. The latter is much more useful when you want to
quickly understand what subtrees have mergeinfo; it's not perfect, but
at least it doesn't induce a migraine :-)
Hmmm, this makes me think that a --quiet option to svn pg might be nice too:
C:\SVN\src-branch-1.5.x>svn pg svn:mergeinfo -Rvq
Property svn:mergeinfo set on '.': svn:mergeinfo
Property svn:mergeinfo set on 'notes\tree-conflicts\scratch-pad.txt'
Property svn:mergeinfo set on 'www\images\subversion_logo_hor-468x64.png'
Property svn:mergeinfo set on 'subversion\bindings\swig'
Property svn:mergeinfo set on 'COMMITTERS'
Property svn:mergeinfo set on 'www\images\subversion_logo-384x332.png'
Property svn:mergeinfo set on 'subversion\libsvn_subr'
Property svn:mergeinfo set on 'subversion\libsvn_wc\adm_ops.c'
Property svn:mergeinfo set on 'CHANGES'
Property svn:mergeinfo set on 'subversion\tests\cmdline\svntest\actions.py'
Property svn:mergeinfo set on 'subversion\libsvn_client\merge.c'
Property svn:mergeinfo set on 'subversion\include\private'
Property svn:mergeinfo set on 'www\images\subversion-diagram.png'
Property svn:mergeinfo set on 'www\images\subversion_logo-200x173.png'
Property svn:mergeinfo set on 'aclocal.m4'
But I digress...
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Julian Foad <ju...@btopenworld.com>.
On Tue, 2009-01-20 at 09:28 -0500, Paul Burba wrote:
> On Tue, Jan 20, 2009 at 8:43 AM, C. Michael Pilato <cm...@collab.net> wrote:
> >> A. Make "propget" print just the plain value with no header when there
> >> is only one target, like it used to, but use the new indented format
> >> when there are multiple targets. Remove the new use of "-v". (Leave
> >> "proplist" as it
> >
> > Do you mean "multiple targets" or "multiple targets with the named
> > property"? Actually, that's not even so very interesting. I guess I don't
> > like the idea that somebody might type:
>
> This is probably the same question as Mike's, but what would a
> recursive propget yield? The same indented output as with multiple
> targets right? I'd hate svn pg svn:mergeinfo -vR to return to the
> mess it was.
I mean whatever the plain (old-style and still default) "propget"
currently does, and I think that is: any invocation that involves
scanning multiple nodes and so may result in multiple outputs.
> > svn propget svn:mergeinfo *.c
> >
> > in one directory, and see one form of output, and then do exactly the same
> > thing in other directory and see another form.
That inconsistency is present in the plain (old-style and still default)
"propget".
- Julian
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1038008
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Paul Burba <pt...@gmail.com>.
On Tue, Jan 20, 2009 at 8:43 AM, C. Michael Pilato <cm...@collab.net> wrote:
> Julian Foad wrote:
>> I think I need to tweak the new indented "svn propget" output format.
>>
>>
>> BACKGROUND
>> ==========
>>
>> 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:
>>
>> In v1.5:
>> [[[
>> $ svn-1.5.4 proplist -v subversion/tests/cmdline/
>> Properties on 'subversion/tests/cmdline':
>> svn:ignore : svn-test-work
>> httpd-*
>> .gdb_history
>> *.pyc
>> ...
>> ]]]
>>
>> In trunk:
>> [[[
>> $ svn proplist -v subversion/tests/cmdline/
>> Properties on 'subversion/tests/cmdline':
>> svn:ignore
>> svn-test-work
>> httpd-*
>> .gdb_history
>> *.pyc
>> ...
>> ]]]
>>
>> 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.
>>
>> In v1.5, and also in trunk without "-v":
>> [[[
>> $ svn-1.5.4 propget svn:ignore subversion/tests/cmdline/
>> svn-test-work
>> httpd-*
>> .gdb_history
>> *.pyc
>> ...
>>
>> $ svn-1.5.4 propget -R svn:ignore subversion/tests/cmdline/
>> subversion/tests/cmdline/svntest - *.pyc
>> *.o
>> ...
>> subversion/tests/cmdline - svn-test-work
>> httpd-*
>> .gdb_history
>> *.pyc
>> ...
>> ]]]
>>
>> In trunk:
>> [[[
>> $ svn propget -v svn:ignore subversion/tests/cmdline/
>> Properties on 'subversion/tests/cmdline':
>> svn:ignore
>> svn-test-work
>> httpd-*
>> .gdb_history
>> *.pyc
>> ...
>>
>> $ svn propget -vR svn:ignore subversion/tests/cmdline/
>> Properties on 'subversion/tests/cmdline/svntest':
>> svn:ignore
>> *.pyc
>> *.o
>> ...
>> Properties on 'subversion/tests/cmdline':
>> svn:ignore
>> svn-test-work
>> httpd-*
>> .gdb_history
>> *.pyc
>> ...
>> ]]]
>>
>> The benefit is seen better with recursive or longer listings, especially
>> with long values like svn:mergeinfo and svn:ignore. (For properties with
>> short names and short single-line values, the old format looks nicer for
>> some purposes.)
>>
>>
>> NOW...
>> ======
>>
>> I don't like using "-v" to change propget's output format, and part of
>> the reason I left it like that is so we can get a feel for which we
>> prefer.
>>
>> I think we should:
>>
>> A. Make "propget" print just the plain value with no header when there
>> is only one target, like it used to, but use the new indented format
>> when there are multiple targets. Remove the new use of "-v". (Leave
>> "proplist" as it
>
> Do you mean "multiple targets" or "multiple targets with the named
> property"? Actually, that's not even so very interesting. I guess I don't
> like the idea that somebody might type:
This is probably the same question as Mike's, but what would a
recursive propget yield? The same indented output as with multiple
targets right? I'd hate svn pg svn:mergeinfo -vR to return to the
mess it was.
> svn propget svn:mergeinfo *.c
>
> in one directory, and see one form of output, and then do exactly the same
> thing in other directory and see another form.
>
>> If you care, please have a look and a think. Alternatives are:
>>
>> B. Leave it as it is.
>
> 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."
I lean in the 'leave it as is' direction too, but as long as there is
some way to get the indented output with both pl and pg then anything
but D is ok with me.
Paul
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by "C. Michael Pilato" <cm...@collab.net>.
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
with --verbose.)
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1038006
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by Julian Foad <ju...@btopenworld.com>.
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")?
- Julian
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1037985
Re: [RFC] New indented propget/proplist output needs a tweak for
v1.6
Posted by "C. Michael Pilato" <cm...@collab.net>.
Julian Foad wrote:
> I think I need to tweak the new indented "svn propget" output format.
>
>
> BACKGROUND
> ==========
>
> 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:
>
> In v1.5:
> [[[
> $ svn-1.5.4 proplist -v subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore : svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> In trunk:
> [[[
> $ svn proplist -v subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> 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.
>
> In v1.5, and also in trunk without "-v":
> [[[
> $ svn-1.5.4 propget svn:ignore subversion/tests/cmdline/
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
>
> $ svn-1.5.4 propget -R svn:ignore subversion/tests/cmdline/
> subversion/tests/cmdline/svntest - *.pyc
> *.o
> ...
> subversion/tests/cmdline - svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> In trunk:
> [[[
> $ svn propget -v svn:ignore subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
>
> $ svn propget -vR svn:ignore subversion/tests/cmdline/
> Properties on 'subversion/tests/cmdline/svntest':
> svn:ignore
> *.pyc
> *.o
> ...
> Properties on 'subversion/tests/cmdline':
> svn:ignore
> svn-test-work
> httpd-*
> .gdb_history
> *.pyc
> ...
> ]]]
>
> The benefit is seen better with recursive or longer listings, especially
> with long values like svn:mergeinfo and svn:ignore. (For properties with
> short names and short single-line values, the old format looks nicer for
> some purposes.)
>
>
> NOW...
> ======
>
> I don't like using "-v" to change propget's output format, and part of
> the reason I left it like that is so we can get a feel for which we
> prefer.
>
> I think we should:
>
> A. Make "propget" print just the plain value with no header when there
> is only one target, like it used to, but use the new indented format
> when there are multiple targets. Remove the new use of "-v". (Leave
> "proplist" as it
Do you mean "multiple targets" or "multiple targets with the named
property"? Actually, that's not even so very interesting. I guess I don't
like the idea that somebody might type:
svn propget svn:mergeinfo *.c
in one directory, and see one form of output, and then do exactly the same
thing in other directory and see another form.
> If you care, please have a look and a think. Alternatives are:
>
> B. Leave it as it is.
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."
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1037937