On 5/9/06, Tsuna <tsuna(a)warszawa.lrde.epita.fr>
wrote:
Hi,
vcs doesn't seem to support svn's option -N
Vcs supports it!
for examples say I have:
? src/sig/Makefile.in
A src/sig
A src/sig/Makefile.am
ATM, I can't commit unless I rm src/sig/Makefile.in
You are not supposed to remove the Makefile.in!
$ vcs-svn ci -N src/sig src/sig/Makefile.am
vcs: info: Updating your working copy...
At revision 7.
? src/tools/Makefile.in
? src/sig/Makefile.in
vcs: error: You have unrecognized files in your working copy!This meant that these files
wo
n't be committed!
You are experiencing a feature of Vcs :) that impose a rule to you:
you can't commit with '?' files. In new_user mode a more complete
explanation is provided. Perhaps you should comment the "new_user:
false" line in your config file :). The good answer for Makefile.in is
to add it to the ignore list `vcs-svn ignore src/sig/Makefile.in' is
your friend.
Hope this helps, and thank you for using Vcs.
--
Nicolas Pouillard aka Ertai <ertai(a)feydakins.org>
http://uttk.org Uttk -- Unified Test Tool Kit
(BTW, a space is missing in your signature, it's "-- " not "--")
I know this is a "feature" of VCS. But I'm telling it not to recurse in
this
directory so ... what the hell?
It's a bit borring to add all the files generated by the autotools in the
ignore list... maybe VCS should help by knowing that this particular file is
generated by auto* and thus ignore it (maybe also display a notice to let the
user know this file was ignored for such reasons)
--
SIGOURE Benoit aka Tsuna
_____
/EPITA\ Promo 2008.CSI Rock & tRoll