In this context I don't mind which is the correct one.
I only would like to know what is supposed to be stored inside the
2.5.59 tarball on kernel.org and what is supposed to be changed between
2.5.59 and the 1.952.4.2 changeset.
The one I see in 2.5.59 (I double checked the tar.gz) is this:
void jfs_truncate(struct inode *ip)
jFYI(1, ("jfs_truncate: size = 0x%lx\n", (ulong) ip->i_size));
block_truncate_page(ip->i_mapping, ip->i_size, jfs_get_block);
And I see no changes in this area starting from 2.5.59, until changeset
1.952.4.2. So I deduce my software is right and that either the 2.5.59
tarball or the 1.952.4.2 changeset are corrupt.
I can't yet fetch a full tree out of bitkepper yet (you know the network
protocol must be reverse engeneered first), I can only fetch
incrementals with metadata and raw patch so far because this is the
thing I care about most, after I've all the changesets in live form in
my db I don't mind too much about the ability to checkout a the whole
tree too, since I can do the same starting from my open db rather than
using the proprietary one.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/