On Fri, Jul 10, 2009 at 6:43 PM, Max Battcher<[email protected]> wrote: > I've got a partial implementation of this myself in my "darcsforge" code. > The pristine object names/hashes as cache keys seems a useful tool for > caching historical data. Dealing with new integration states (er, revisions) > is easy (during a cache walk through pristine), and I was fretting how to > deal with historical integration states but just recently had some ideas > involving context file caching. > > I certainly think that modeling revision tracking around pristine.hashed is > the current best way forward. I do feel for those that haven't thrown out > the bathwater and trying to shoehorn such a solution into a traditional > revision number/hash-based design. I think gitit would be a different animal > if it were designed with darcs in mind from the beginning.
I'm just a humble filestore dev, but when I look into pristine.hashed, aren't I seeing hashes like that filestore/gitit use? I don't really see what alternative model there is - Orchid started with Darcs, after all, and switching to filestore made it *better*, so just starting with Darcs doesn't lead to any obviously better functionality. -- gwern _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
