Am Donnerstag, 17. August 2006 21:25 schrieb Philipp Marek: > parameters I could reproduce your problem; fsvs didn't find the entry > because it thought that it should be ignored.
Well, .kde does match an ignore entry in fact. Reading the docs I got the impression that ignore patterns only avoid new matched files being noticed and commited by fsvs, and not causing problems with already managed ones? I understood that also the "fsvs add" was implemented to utilize this behaviour and to force some otherwise ignored files to be managed anyway. Am I right the way I understood how it should happen, or am I trying to misuse the "ignore"-feature? The ignore-entry in question is "./.*", which of course matches anything starting with ".kde". (And it is supposed to.) > *My* problem is, that was on a ramfs and the processor freezed once > again .... So I'll have to try again. :-( > > > What happens on a new "fsvs sync-repos"? > Take your time. I also just had a hard freeze during sync-repos. :-/ I hope this doesn't damage some internal data structures of fsvs' WAA? I simple rebootet and reinitiated the sync-repos run which correctly restarted from the beginning. Greetings, Gunter -- *** Powered by AudioScrobbler --> http://www.last.fm/user/Interneci/ *** 23:03 | Within Temptation - Jillian (I'd Give My Heart) 22:58 | Within Temptation - Stand My Ground 22:51 | Within Temptation - Deceiver of Fools 22:47 | Asp - Ich will brennen *** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
pgp2XzrJTbmoH.pgp
Description: PGP signature
