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/2011-March/109834.html below:

[Python-Dev] Submitting changes through Mercurial

[Python-Dev] Submitting changes through Mercurial [Python-Dev] Submitting changes through Mercurial"Martin v. Löwis" martin at v.loewis.de
Tue Mar 22 20:59:54 CET 2011
>     Senthil> You will have to 'push' your changes to those so that they are
>     Senthil> publicly visible and then point that url in the bug-tracker.
> 
> I can see this turning into a giant bowl of spaghetti.  How in the world are
> people supposed to understand how all these repositories are related to each
> other?

Yes, it will turn into a giant bowl of spaghetti - that's the whole
point of "Distributed" version control systems.

So: don't bother about this. There is certainly going to be a lot of
repository that you don't know about, just as you didn't know about
patches that may have circulated before. If people want you to know
about a clone, they have to tell you - one way of doing that is to
attach its link to a tracker issue.

> The Roundup interface is getting extraordinarily messy.

So what is your constructive proposal?

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