> and then you added one change below that, multiple times. If you were to
> combine all of those changes in a BK tree, it would look like
> [older changes]
> [sched1] [sched2] [sched3] [sched4] [sched5] [sched6] [sched7]
I'm porting rmap to 2.5 now, doing just this.
One thing I noticed was that the space usage of all the
bk trees I'm using in order to keep the different changes
individually pullable is about 1.5 GB now.
Not too big an issue for me, but it might be an issue if
every bkbits.net user starts doing this ... ;)
-- "Linux holds advantages over the single-vendor commercial OS" -- Microsoft's "Competing with Linux" document
- 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/