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/101417.html below:

[Python-Dev] Mercurial migration readiness

[Python-Dev] Mercurial migration readiness [Python-Dev] Mercurial migration readiness"Martin v. Löwis" martin at v.loewis.de
Sun Jul 4 00:51:58 CEST 2010
>>> I'd love to see a more detailed description of this, including why
>>> someone new to Mercurial would choose one over the other.
> 
>> I think someone new to Mercurial shouldn't choose either one.
> 
>> Just sit back and wait for the real migration to happen.
> 
> 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. 

I think your description already falls into the "advanced user"
category. The new-to-mercurial committer should (IMO) use a "what if it
still was svn" workflow, which uses hg pull/up/commit/push. That can
only work if pushing really has the desired effect, which isn't the case
for any of the installations that we operate.

When the test-for-two-weeks installation becomes available, the
new-to-hg users will have a chance to learn how to use it without fear
of breaking anything. Until then, they should just remain patient.

Regards,
Martin
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