Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\,RFC\]\s+Factor\s+some\s+btree\s+code\.\.\.\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\,RFC\]\s+Factor\s+some\s+btree\s+code\.\.\.\.\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH,RFC] Factor some btree code.... (score: 1): Author:; Date: Wed, 21 Nov 2007 15:20:06 +0000; I like this. But I think a single set of xfs_btree_ops would be a lot more readable. Also I'm not sure we actually need all these ops, e.g. instead of .buf_to_block we could always just call XFS_BUF_; /archives/xfs/2007-11/msg00198.html (7,577 bytes)
2. Re: [PATCH,RFC] Factor some btree code.... (score: 1): Author:; Date: Thu, 22 Nov 2007 08:42:08 +1100; I've already converted it to a single ops structure and cut out quite a few ops that could be generic (sibling ops, checking ops, numrecs ops, etc). I opted for moving them all over initially and now; /archives/xfs/2007-11/msg00206.html (8,394 bytes)
3. Re: [PATCH,RFC] Factor some btree code.... (score: 1): Author: ); Date: Wed, 21 Nov 2007 15:20:06 +0000; I like this. But I think a single set of xfs_btree_ops would be a lot more readable. Also I'm not sure we actually need all these ops, e.g. instead of .buf_to_block we could always just call XFS_BUF_; /archives/xfs/2007-11/msg00514.html (7,577 bytes)
4. Re: [PATCH,RFC] Factor some btree code.... (score: 1): Author: >; Date: Thu, 22 Nov 2007 08:42:08 +1100; I've already converted it to a single ops structure and cut out quite a few ops that could be generic (sibling ops, checking ops, numrecs ops, etc). I opted for moving them all over initially and now; /archives/xfs/2007-11/msg00522.html (8,394 bytes)

Current List: 1 - 4
Page: [1]