On Thursday 17 August 2006 23:31 Gunter Ohrner wrote:
> 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?
No, you're completely right.
> The ignore-entry in question is "./.*", which of course matches anything
> starting with ".kde". (And it is supposed to.)
Yes.
> > *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?
Hmmmm ... is there some freeze_processor() in sync.c? :-)
No; all directory data is written to a temporary file, and renamed if
finished. So this should do no bad things.
> I simple rebootet and reinitiated the sync-repos run which correctly
> restarted from the beginning.
OK. Thank you for your help!
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
