On Sat, 26 May 2007, Dana How wrote: > On 5/26/07, Nicolas Pitre <nico@xxxxxxx> wrote: > > In other words, I think the naughty blob could simply be recognized as > > such and be referenced in a special list instead of being written out > > initially. Then when everything is believed to be written, the special > > list can be walked to force write those naughty blob at last. No need > > to modify the current object order. > This works as long as a naughty blob can't be a delta base for a nice blob > (causing it to be pushed out early by the recursion in write_one()). > I think that's a reasonable and understandable restriction. Sure. Or the delta can inherit the naughty property if its base is also naughty, which solves the problem nicely. Nicolas - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
