[Python-Dev] Mercurial migration readiness (original) (raw)
Daniel Stutzbach daniel at stutzbachenterprises.com
Sat Jul 3 23:51:58 CEST 2010
- Previous message: [Python-Dev] Mercurial migration readiness
- Next message: [Python-Dev] Mercurial migration readiness
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Jul 3, 2010 at 11:36 AM, Tres Seaver <tseaver at palladion.com> wrote:
- - Create a "pristine" clone of the trunk (one where I never commit any changes):
$ cd $pythonrepo $ 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
My question is basically the same as Terry Reedy's, but I'm going to phrase it a bit differently:
This is perhaps a naive question, but why do you create a second local clone instead of just creating a branch?
Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises, LLC <http://stutzbachenterprises.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100703/64a6e65e/attachment.html>
- Previous message: [Python-Dev] Mercurial migration readiness
- Next message: [Python-Dev] Mercurial migration readiness
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]