"svn commit -N" broken?

[Michael Schmitt <sc...@TI.Uni-Trier.DE>]

Hello,

using svn 0.23, "svn commit -N" and "svn commit -N . " have no effect, 
even if there are modified in the current directory. I guess this is a 
bug, isn't it?

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: "svn commit -N" broken?

[Ben Collins-Sussman <su...@collab.net>]

Michael Schmitt <sc...@TI.Uni-Trier.DE> writes:

> Hello,
> 
> using svn 0.23, "svn commit -N" and "svn commit -N . " have no effect,
> even if there are modified in the current directory. I guess this is a
> bug, isn't it?

Nope, at the moment, we've defined 'svn ci -N' to mean depth 0.  That
is, it's only used to commit the directory itself (assuming you've
made a propchange on it).

Yes, it's inconsistent with other uses of -N.  And this is why I
believe we're switching to a --depth {0, 1, infinity) model.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org