Hello Gunnar!
> So ignoring mtime globally is my only option, at least I know its possible. Do
> you think this can become a match pattern so that it can be used together with
> "dironly" in a global scope affecting all dirs?
No, you're misunderstanding me.
"dironly" and match patterns are used only for new files, that are not yet
known in the
repository.
The filter specifies what to look for in *known* files.
>> Maybe ...
>> The symlinks are there just for informational purposes, and so they might
>> stay.
>> If there's only a sqlite database, it's not that easy to see which working
>> copy this
>> is.
>> Maybe I should put a "README" or something like that in there? But that's
>> not so
>> easily
>> used by scripts ...
>
> Just asking because we had problems with the _base symlink when debian
> packages
> take use of the "find" command. This still happens with "base-files" causing
> an
> endless loop.
You can just remove them ... FSVS doesn't use them.
>>> I get a segfault with "fsvs unversion", bugreport is on its way...
>> Fine ;-/, please tell me.
>
> This happens when using the "fsvs add" and performing unversion. I have to
> figure out the exact scenario.
Thank you!
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=2414420
To unsubscribe from this discussion, e-mail:
[[email protected]].
