Hi Nathaniel, Glad to see you're still following the issue992 stuff :-)
On Thu, Jul 23, 2009 at 16:51:47 -0400, Nathaniel W Filardo wrote: > > Certainly one possible solution here would be to simply carry over the > > Hash: lines from the darcs-2 inventory format as (optional) hints for > > file paths in context files. Considering the otherwise congruency of the > > context and inventory files I would hope this might be something easy to > > achieve (and would be useful generally), and I'm hoping the reason it > > hasn't been done is simply because it hasn't thought to be done. > > While we're talking about revving the storage, would it be feasible to > switch _all_ references to patches to be by hash only? Note the file hash ties us to a particular instance of a patch. If we commute the patch, it gets a different file hash so I don't think this would give us enough information to work with. For the interested: http://wiki.darcs.net/Hashes > Of course, upon receiving a context or list of objects represented this way, > the current equivalence classes would still need to be calculated by opening > the object by hash and reading the patch info. That doesn't seem too bad... > it might be a large number of file opens until hashed-storage indexes things > this way? (I was under some impression that it was going to; if that's > mistaken, please let me know.) The problem with using just the file hash is that the object you want may just not be on the repository you're reading from. You may be able to reconstruct it through commutation, but then you'll need the regular patchinfo stuff to do that. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpK5JlIq4yHd.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
