[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bitkeeper-users
Subject:    Re: [Bitkeeper-users] Windows question
From:       mru () kth ! se (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=)
Date:       2004-02-26 9:24:51
Message-ID: yw1xu11ei464.fsf () kth ! se
[Download RAW message or body]

Larry McVoy <lm@bitmover.com> writes:

> On Tue, Feb 24, 2004 at 03:58:05PM +0100, M?ns Rullg?rd wrote:
>> > If you see "foo.c 1.5: 83 lines" then it has already written and closed 
>> > the file.  We simply don't get to that code path unless we've done so.
>> 
>> It does print that line before make prints the compilation command.
>> 
>> > I'd also try this on some other file system than XFS.
>> 
>> I've seen it on ext3 too.  How could the filesystem possibly make a
>> difference?
>
> I dunno, but I've had reports of XFS eating BK trees before (it was a long 
> time ago).  Seems darned unlikely, I agree.

Nothing is eating the trees.  They are in perfectly good shape even
after the build failure.  It's probably a problem with kbuild rather
than BK.

-- 
Måns Rullgård
mru@kth.se

_______________________________________________
Bitkeeper-users mailing list
Bitkeeper-users@bitmover.com
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.
[prev in list] [next in list] [prev in thread] [next in thread]