Yes I already know that very sad behavior...
Thanks for the report.
On 2/14/06, Roland Levillain <roland(a)lrde.epita.fr> wrote:
The `--non-recursive' option (short option:
`-N') doesn't work on
`vcs-svn commit'.
For instance, lets say my working copy contains a new directory and
three new files within this directory:
A tests
A tests/is_a.cc
A tests/properties.cc
A tests/if.cc
A tests/typedef.cc
I just want to commit `tests/if.cc' and `tests/typedef.cc'. With
plain svn, I must mention `tests' in the list of
files-to-be-committed; but to avoid the checkin of `tests/is_a.cc' and
`tests/properties.cc' (due to the default recursive behavior of `svn
commit'), I have to add `--non-recursive' to the command line as well.
This doesn't work with Vcs' front-end to svn (vcs-svn): the
`--non-recursive' option is thrown away and svn adds `tests' and its
files recursively.
I also tried to omit `test' in the vcs-svn command line, but the
result is the same as with vanilla svn: that's forbidden.
[...]
svn: Commit failed (details follow):
svn: '/home/levill_r/src/oln-1.0/metalic/tests' is not under version control and
is not part of the commit, yet its child
'/home/levill_r/src/oln-1.0/metalic/tests/typedef.cc' is part of the commit
(An obvious workaround is to move away new/modified files from
the working copy at checkin time, but that's quite a regression from
plain svn!).
_______________________________________________
Projects mailing list
Projects(a)lrde.epita.fr
https://www.lrde.epita.fr/mailman/listinfo/projects
--
Nicolas Pouillard aka Ertai <ertai(a)feydakins.org>
http://uttk.org Uttk -- Unified Test Tool Kit