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

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

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2004-03-05 14:53:25 CET

C.A.T.Magic wrote:
>
> 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

The addition of flags to modify a program's behaviour is not something to be taken lightly. I expect you are thinking that there is a simple definition of "file that exists in the working dir AND is under version control". You could certainly come up with a definition, but it would not be useful for all purposes. For example, to decide which files to commit, you wouldn't want just those files, you would also want to include files that do not exist in the working directory because they are scheduled for deletion from version control.

> " 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.

"svn status" is the command for getting this information. You can remove the status characters in front if you don't care whether a file is sheduled for addition, deletion or something else; but I suspect that actually in many cases you would care.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 6 02:02:56 2004

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