Re: [9fans] replica (was: ipv6)

["Chris Hollis-Locke" <chris@cjl1.demon.co.uk>]

So I can get incompatible files in 'partial' updates:
- current log tells me I need foo.h and foo.c
- pull gets foo.h
- someone updates foo.h and foo.c (but wont enter log until next
cron run)
- pull then gets (newer) foo.c

I've now got a wrong foo.h/foo.c pair and they wont compile.

My foo.h is correct as per the log info
Pull can spot that foo.c is more up to date but without
dependency info cannot determine that it needs to re-fetch foo.h

This is resolved by re-running pull after the next log update.
This raises two questions:
How do I know when the log is up to date (mk scan has run)?
How do I know if I have to schedule a new pull because I got a
'partial' update?