From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] changing file ownership with fossil?
Date: Wed, 15 Oct 2003 06:43:01 +0100 [thread overview]
Message-ID: <ed9324b151a4fed195ec01bcfa859a6a@caldo.demon.co.uk> (raw)
In-Reply-To: <20031015023615.GA12630@nerds.cs.umd.edu>
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.
next prev parent reply other threads:[~2003-10-15 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 0:19 Tim Fraser
2003-10-14 2:24 ` jmk
2003-10-15 2:36 ` Tim Fraser
2003-10-15 3:09 ` Russ Cox
2003-10-15 5:43 ` Charles Forsyth [this message]
2003-10-15 14:25 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed9324b151a4fed195ec01bcfa859a6a@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).