From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] changing file ownership with fossil? From: Charles Forsyth In-Reply-To: <20031015023615.GA12630@nerds.cs.umd.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Wed, 15 Oct 2003 06:43:01 +0100 Topicbox-Message-UUID: 6ef2002e-eacc-11e9-9e20-41e7f4b1d025 there are changes for -W in several fossil files, including 9srv.c, and pull probably didn't update that one. less clear is why the updated binary didn't work, unless that too isn't up to date. you could cmp yours against sources. replica checks the mtime and length to decide that a file has changed, so if it couldn't set mtime correctly in a previous run, things might well go wrong in a subsequent one. by coincidence, for something i am doing, i was going to change replica/applylog to allow an optional extra field containing a hash of a file, to allow more accurate detection of changes. i was also trying to decide whether the database was really needed.