Hi Very thanks for your answer >> >> 1.How can I add files and directories recursive? (sometimes I must >> commit about hundreds files and directory). I always do 'find ./ |xargs >> fsvs add' but is it sole solution (with use external binary) ? >> > You don't need to ... just do a commit, and FSVS will take all new files > automatically, and remove files that no longer exist. > > Doing "find" with large trees is not what I wanted ;-) > OK, but what in case when I want commit only part files? For example I work with new 200 files and I want commit only 150 files, because rest of files are not ready to commit ? >> 16:13:14.270 up__parse_prop[update.c:153] got NULL property for etc: >> svn:text-time >> Segmentation fault >> > Hmmm ... I'll take a look. Why do you have this property removed? Did you do > that manually? > > No, I did not.
This problems showed when 2 persons commit. I must describe this case: For example: We have 2 machine A and B. And machine A commit revision 1234, next machine B commit revision 1235, next machine A commit 1236 without fsvs up. Machine A want commit 1235.When I do 'fsvs up' does not update commit 1235. How can I do this? Must I do "fsvs up" before each commit? >> 2.When I try fsvs status (which some changes) I sometimes get >> segmentation fault: >> > ... > >> 19:31:33.610 waa__update_dir[waa.c:1469] update_dir: direnum found 0; >> old has 2 (0) >> 19:31:33.610 waa__update_dir[waa.c:1592] update_dir reports 0 new found, >> status 0 >> 19:31:33.610 st__status[status.c:275] INTERNAL BUG >> sts->was_output >> ./usr/local/include was already output .. >> > This is clearly an internal error when doing the tree walking. > > You have removed files like usr/local/include/atalk/compat.h ; does > usr/local/include/atalk still exist? Does usr/local/include/ include exist? > > I moved files from /usr/local/include/atalk to /usr/local/netatalk/include/atalk ------------------------------------------------------ http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=1290329 To unsubscribe from this discussion, e-mail: [[email protected]].
