svn log vs. svn proplist

[Ken Johnson <KJ...@eclypse.org>]

Hello,

Can someone help me understand a difference in
behavior between svn log and svn proplist?  It
would be helpful to me to understand the reasoning
behind these differences so I can learn to predict
(and explain to others) how svn will work.

"svn log" with no path arguments performs the useful
function of displaying commit log messages for files
under version control within a working directory.

"svn proplist" with no path arguments seems to be
a no-op.  "svn proplist *" tries to show properties
for all files in the current directory, which outputs
an error message and stops when it finds a file
which is not under version control (like emacs 
backup files -- .py~, etc.)

I can display the properties of files under version
control with

svn list | xargs -iXX svn proplist "XX"

but I confess this was not the first thing I tried.

KLJ




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn log vs. svn proplist

[Ben Collins-Sussman <su...@collab.net>]

On Mon, 2004-06-14 at 15:35, Ken Johnson wrote:
> Hello,
> 
> Can someone help me understand a difference in
> behavior between svn log and svn proplist? 

All svn subcommands operate on targets.  If you don't specify any
targets, a default target of '.' is assumed.  If you pass '*', then it
will try to run on every target (your shell will expand the *).

> "svn log" with no path arguments performs the useful
> function of displaying commit log messages for files
> under version control within a working directory.

Correct.  You're running 'svn log .', which will show every revision in
which '.' -- or something below it -- changed.


> "svn proplist" with no path arguments seems to be
> a no-op. 

The 'proplist' command shows all properties attached to a versioned
object.  If you pass it multiple targets, it loops over the targets and
shows the properties attached to each one.

'svn proplist' is the same as running 'svn proplist .'  If the current
working directory has no properties attached to it, you see nothing. 
There's nothing to print.

>  "svn proplist *" tries to show properties
> for all files in the current directory, which outputs
> an error message and stops when it finds a file
> which is not under version control (like emacs 
> backup files -- .py~, etc.)

Now you're running proplist on every object in the directory.  Running a
subversion command on an unversioned object produces an error.  Granted,
we probably shouldn't stop looping over the targets when we get an
error.


> 
> I can display the properties of files under version
> control with
> 
> svn list | xargs -iXX svn proplist "XX"

Sure, because 'svn list' is guaranteed to show only version-controlled
objects.  So no errors.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn log vs. svn proplist

[Dominic Anello <da...@danky.com>]

On 2004-06-14 15:35:16 -0500, Ken Johnson wrote:
----8<---- 
> "svn proplist" with no path arguments seems to be
> a no-op.  "svn proplist *" tries to show properties
> for all files in the current directory, which outputs
> an error message and stops when it finds a file
> which is not under version control (like emacs 
> backup files -- .py~, etc.)
> 
> I can display the properties of files under version
> control with
> 
> svn list | xargs -iXX svn proplist "XX"
> 
> but I confess this was not the first thing I tried.
> 
> KLJ

"svn proplist" with no args gets the proplist for the current directory.
If you would like to see the properties defined for every file and
directory in a working copy, try "svn proplist -R"  This will recursively
descend into child directories as well.  AFAIK there is no svn option to
get just the properties of files in the current directory
non-recursively.

-Dominic