On Mon, 5 Dec 2016 at 04:14 Antoine Pitrou <solip...@pitrou.net> wrote:
> On Sun, 04 Dec 2016 00:40:49 +0000 > Brett Cannon <br...@snarky.ca> wrote: > > - I got the code for hg.python.org/hglookup > > - Asking if there's any reason I can't post it publicly > > None than I can think of. > > > - Need to figure out the best way to extract all commit IDs from a > > Mercurial repository > > Probably iterate over all entries in the revlog and inspect the "extra" > field as is done in hglookup? That way you can build a static mapping > of SVN rev -> hg changeset ID, and save it e.g. to a file. > > > - Need to update the code to use the commit IDs (both 12 and 40 > > character lengths) for linking to hg commits > > - Need to update the code to accept 10 or longer hashes from git > > (default used to be 7, but git 2.11 now calculates the shortest, > > unamibiguous hash and CPython is big enough to need 10 characters) > > I'm not sure I understand those two points, but that probably doesn't > matter. > hg.python.org/lookup says any hexadecimal number that is 12 or 40 digits is an hg commit ID, but git uses 10 or 40 digits for our repo for a commit hash. The 10 digit and 12 digit lengths don't clash but the 40 digit one does.
_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
