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/2014-December/137389.html below:

[Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

[Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and GithubEric Snow ericsnowcurrently at gmail.com
Mon Dec 1 02:44:48 CET 2014
On Sun, Nov 30, 2014 at 6:40 PM, Donald Stufft <donald at stufft.io> wrote:
> I’m not sure if it got lost in the discussion or if it was purposely left
> out. However I did come up with another idea, where we enable people to make
> PRs against these repositories with PR integration within roundup. Using the
> fact that it’s trivial to turn a PR into a patch core contributors (and the
> “single source of truth”) for the repositories can remain Mercurial with
> core contributors needing to download a .patch file from Github instead of a
> .patch from from Roundup. This could allow non-committers to use git if they
> want, including PRs but without moving things around.

Hah.  I just had a similar idea.

>
> The obvious cost is that since the committer side of things is still using
> the existing tooling there’s no “Merge button” or the other committer
> benefits of Github, it would strictly be enabling people who aren’t
> committing directly to the repository to use git and Github.

This is not an added cost.  It's just the status quo and something
that can be addressed separately.

-eric
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