"Francois Beausoleil" <fbos@users.sourceforge.net> writes:
> Hi !
>
> I just tried a non-recursive commit for a folder. The command line
> client just returned, as if there were no files to commit... Here's a
> transcript of what happened:
> K:\leadmanagement>svn info
> Path:
> Url: http://svn.hopto.org:8193/repos/rac/leadmanagement/trunk
> ...
>
> K:\leadmanagement>svn st
> M src\java\core\jobnudge\Contact.hbm.xml
> M src\java\core\jobnudge\Contact.java
> M src\java\core\jobnudge\User.java
> M src\java\core\jobnudge\servlets\NewContact.java
> M src\web\enter\application\newcontact.jsp
>
> K:\leadmanagement>svn commit --non-recursive src\java\core
Riiiiiight. And did you notice that none of src\java\core's immediate
children were modified? Are you familiar with what "non-recursive"
means?
Actually, to be fair, 'svn commit' does behave a little different with
respect to the --non-recursive flag. While most subcommand use this
flag to mean "target and its immediate non-directory children", commit
uses it to mean just "target".
> Should I file an issue for this ? I did not find anything with
> "recursive" in the summary that related to commits.
This is not a bug. Do not file an issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 21 04:00:16 2003