8000 Update gitdevs.rst to point out that only ancillary repos still use hg by brettcannon · Pull Request #73 · python/devguide · GitHub
[go: up one dir, main page]
Skip to content

Update gitdevs.rst to point out that only ancillary repos still use hg #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 28, 2016
Merged

Update gitdevs.rst to point out that only ancillary repos still use hg #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 8 additions & 12 deletions gitdevs.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,18 +13,14 @@ Mercurial for git developers
Overview
========

This guide is geared towards prospective contributors who are accustomed to
git-based development. The intention of this guide is to lower the initial
barrier of entry for prospective contributors in learning a new source control
tool. While there are projects that focus on automating this to allow seamless
bridges between the two systems, this guide focusses solely on native Mercurial
functionality. As with most tools, this is not the only method of achieving
git-like workflows with Mercurial. It is intended solely to provide one
potential path.

Note that this geared towards prospective contributors and the patch workflow.
Core developers will have a similar workflow, but it will differ in the later
stages (merge vs patch generation).
This document is meant to help familiarize developers who are used to
a Git-based workflow with Mercurial. While most of the work for Python
is now done in Git, there are a couple ancillary repositories that
still use Mercurial, and thus this document exists those who wish to
help with those ancillary repositories. This does mean, though, that
the examples using the ``cpython`` repositories are purely for
illustrative purposes and people should not use the Mercurial
repository referenced in this document!

The workflow that will be used as the case study for this guide is as follows:

Expand Down
0