Am 18.11.2012 10:00, schrieb Armin Rigo: > Hi, > > On Sun, Nov 18, 2012 at 8:22 AM, Georg Brandl <g.bra...@gmx.net> wrote: >> One way would be to use one hg repo per version, and (maybe, if needed) >> a master repo that has them as subrepos. > > Or have all versions in the same repo as usual (with branches), but > have hg subrepos point to different repos: ones extracted from the > main repo by containing only the correct branch. But it might be a > bit delicate to pull this off. (hg clone takes a "-r" option and > copies only things needed for the given revision or branch, but > apparently we can't pass this option automatically to the cloning of > subrepos. (Maybe it points out that subrepos are a hack best done > without altogether, which is what we did in pypy.))
Yep. Anyway, if every external version goes into a branch, then we don't need subrepos anyway. That is a better idea than mine. Since you can use (e.g.) "hg clone -r tk-8.5" or download a tarball specific to a branch, nobody should need to get the whole externals history on clone. Georg _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
