Stuart Rackham wrote:
[...]
Here's another of my replies that was dropped:
I've received both your replies, directly. The one you repeat here was
received at 0542 local time, while your repeat was received 0628. I
don't think they're being dropped, just delayed.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─
Hi all,
I've had the following error, and I don't know why and I don't know what it
really means and I don't know what to do about it! (yes, I really don't know!)
ERROR: [mefs1a.c] is different on disk compared to the repository
NOTICE: Repository version of [mefs1a.c] stored in
On Fri, Aug 24, 2012 at 6:57 PM, Richard Hipp d...@sqlite.org wrote:
Apparently when it looked at the file that was committed to the repository
as mefs1a.c that file was different from what it saw on disk. The
version of the file that it tried store in the repository is now copied
into
On Fri, Aug 24, 2012 at 07:32:18PM +0200, Stephan Beal wrote:
On Fri, Aug 24, 2012 at 6:57 PM, Richard Hipp d...@sqlite.org wrote:
Apparently when it looked at the file that was committed to the repository
as mefs1a.c that file was different from what it saw on disk. The
version of the
On Fri, Aug 24, 2012 at 8:32 PM, Lluís Batlle i Rossell vi...@viric.namewrote:
Very weird. What OS works so bad? The filesystem has traditionally been a
kind
of IPC, and in your situation, that can't work at all.
In my particular case i'm afraid the hard drive is slowly failing (but i
don't
On Friday, August 24, 2012 6:57 PM, Richard Hipp wrote:
On Fri, Aug 24, 2012 at 12:45 PM, Andy Gibbs wrote:
Hi all,
I've had the following error, and I don't know why and I don't know what
it really means and I don't know what to do about it! (yes, I really
don't know!)
ERROR: [mefs1a.c]
Fossil keeps track of which files have changed (by default) by looking at
the file size and the mtime. If neither the file size nor the mtime have
changed, fossil (by default) assumes that the content of the file is also
unchanged.
Perhaps your edit somehow preserved both the file size and mtime
7 matches
Mail list logo
