A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-July/101415.html below:

[Python-Dev] Mercurial migration readiness

[Python-Dev] Mercurial migration readiness [Python-Dev] Mercurial migration readinessDaniel Stutzbach daniel at stutzbachenterprises.com
Sat Jul 3 23:51:58 CEST 2010
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 $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
>

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>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4