Re: [9fans] changing file ownership with fossil?

["Russ Cox" <rsc@swtch.com>]

> i was also trying to decide whether the database
> was really needed.

without the database you only have two pieces
of information per file -- the mtime/length on the
local system and the mtime/length on the remote system.
a comparison between these two can only have two
outcomes, whereas there are three outcomes in the current
system:

	- file is outdated, needs updating
	- file is fine, no updating
	- file is outdated but locally changed, warn user

by storing a complete history of files given out
on the server, you could avoid storing the local
information, but that requires the server knowing
more about its clients than it currently does.
right now the per-client data is all on the clients,
and the server is "stateless" as it were.
(the database on the server could be
removed if you redefine mtime on directories
properly.)