Re: Why do commands fail when a file is unknown to svn?

>> why not provide an extra flag like
>> svn --ignore-unknown-files
>> ?

> I will veto this. We don't need another configuration switch to
> accomodate what is essentially a misuse of Subversion (See my previous
> email for more info).

Maybe I misunderstood the use case in the original post --
your veto is ofcourse correct.

if I now get it right,
> svn ls
will access -the server- and list all files under revision control there
and not all files 'that exist in the working dir AND are under version
control'

so...
how about some extra flags for
  " list --version-controlled-files-in-working-dir "
this would then probably be somewhat similar to
  " status --without-the-single-characters-in-front "
 (ofcourse something shorter would be nice:)

this kind of ls would work without access to the remote repository
and also allow easier use in some scrips and shell commands.

---
And while I may have the ear of an svn developer --
   svn ls -N   <--- unsupported/error (nonrecursive is default)
   svn ls -R
   svn add -N
   svn add -R   <--- unsupported/error (recursive is default)
why are the some functions that default to "-R"ecursive and
some other that default to "-N"onrecursive,
but either one complains when used when the default -R and -N
is explicitly specified -- this is sometimes annoying
because you have to remember whether a command requires an
-R,  -N or nothing all the time.
( is this filed as an issue or as a nono-decision already?
  I couldn't find anything on the topic yet )
thanks to the svn developers for this great product :-)
=====
c.a.t.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org