On 7/3/2010 12:36 PM, Tres Seaver wrote:
I would say that using the SVN mirror is a fine way to experiment with
using hg against the Python sources to develop and test patches. Here
is the setup I have used for work against trunk (I have a parallel pair
of repositories for the release2.6-maint branch):
- - Create a "pristine" clone of the trunk (one where I never commit any
changes):
$ cd $python_repo
$ hg clone http://code.python.org/hg/trunk/ pytrunk-upstream
- - Create a local clone from that repository:
$ hg clone pytrunk-upstream pytrunk-work
$ ./configure&& make
Before working on a patch, I refresh the upstream repository:
$ cd $python_repo/pytrunk-upstream&& hg pull
and pull any changes into the local working repository:
$ cd $python_repo/pytrunk-work
$ hg pull -u
$ make
This is perhaps a naive question, but hat do you gain with the
intermediate mirror clone of upstream? (Other than filling more of your
disk?)
--
Terry Jan Reedy
_______________________________________________
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
