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

You could do this:

--- Begin file isversioncontrolled ---
#/bin/bash
svn info $1 &>/dev/null
--- End of file

svn ci $( find . -name Makefile -exec isversioncontrolled {} \; -print )

Of course, if 'svn info' would support a -q option that didn't print
anything, you wouldn't need the script (hint, hint).

 - James

-----Original Message-----
From: Nicolás Lichtmaier [mailto:jnl@synapsis-sa.com.ar]
Sent: Thursday, March 04, 2004 9:49 AM
To: dev@subversion.tigris.org
Subject: Why do commands fail when a file is unknown to svn?

In CVS, if I want to do a modified Makefiles only commit, I can always
do: cvs commit $( find . -name Makefile ) (The same works with diff and
other commands). CVS will ignore any file which is not under revision
control. I can't do this in SVN, so I can't find an easy way to continue
working the same way.

Is this intended for any reason? Could this be changed? Do I file a bug
report? =)

Thanks!

-- 
Nicolás Lichtmaier.-
Synapsis Argentina
+54(11)4314-3000 (int. 231)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org