Hello Maurice!
On Saturday 09 August 2008 Maurice van der Pot wrote:
> On Sat, Aug 09, 2008 at 08:36:21AM +0200, Philipp Marek wrote:
> > I think what you're seeing is a problem I'm hunting just now -
> > that some filter settings cause commit not to work as expected.
> >
> > Please try these commands:
> > fsvs info .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign
> > (and send me the output), and
>
> [EMAIL PROTECTED] ~> fsvs info .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign
> .... 1129 .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign
...
> Repos-MD5: 8b2c297da63b650766423f6736c76093
...
> [EMAIL PROTECTED] ~> md5sum .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign
> 8755e0a3395d074aa2451b326645ff04 .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign
So the entry is changed, but not seen as such - because the size and mtime are
identical.
> > fsvs ci -o empty_commit=no -C -f text,owner,group,mode
> > .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign -C
> > Does that commit the file?
>
> Yes it does.
Ok, so the MD5 check (with -C -C) still works - that's at least a workaround.
> > What version are you running?
>
> fsvs reports version trunk:1777, but my svn checkout is revision 1820
> and I think that's what it was built from.
Now that I think about that again I think I know what the problem is ...
To do the filtering on eg. "-ftext" FSVS has to know what has changed, and so
the internal meta-data storage might already be updated - and if the file
doesn't get committed (because it hasn't changed after all) the updated
meta-data gets written to the entry list.
Could you try updating to HEAD, do a "sync-repos" and re-try the "status"?
I'll try to get the commit-filter problem fixed.
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]
