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

Re: problem with 'svn list --verbose'

From: Lorenz <lorenznl_at_yahoo.com>
Date: 2006-11-16 08:19:05 CET

Ryan Schmidt wrote:
>On Nov 15, 2006, at 01:38, Lorenz wrote:
>> ru_RU.Subversion wrote:
>>
>>> A have a trouble. Results of "svn list --verbose" and "svn list --
>>> verbose *.*"
>>> shows different filelists. Look at this:
>>> [...]
>>> Is this bug or feature?
>>
>> "svn list" shows informations about the files in the repository, not
>> files in the working copy.
>>
>> "svn list -v" is equivalent to "svn list -v ." and therefore lists
>> the contents of the repo folder the working copy was checked out from.
>>
>> "svn list -v *.*" on the other hand will only list information from
>> the repo for files files that are already in the working copy.
>
>False. "svn list" most definitely does operate on the working copy,
>unless you provide a URL of a repository, in which case it lists the
>repository.

Well, then I must have missunderstood:

<svn list --help>

list (ls): List directory entries in the repository.
usage: list [TARGET[@REV]...]

  List each TARGET file and the contents of each TARGET directory as
  they exist in the repository. If TARGET is a working copy path, the
  corresponding repository URL will be used. If specified, REV
determines
  in which revision the target is first looked up.

  The default TARGET is '.', meaning the repository URL of the current
  working directory.

</svn list --help>

Doen't that mean, that even if you provide a wc path as target, the
listed informations are from the corresponding repository location?

yours confused
     Lorenz

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 16 08:19:52 2006

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

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