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

[Python-Dev] Using feature branches for local development

[Python-Dev] Using feature branches for local development [Python-Dev] Using feature branches for local developmentNick Coghlan ncoghlan at gmail.com
Sun Mar 13 12:25:46 CET 2011
I'm experimenting with creating some local branches for things I'd
like to work on during the sprints this week, and have a couple of
questions about the associated workflow.

1. While the feature branches are active, is it correct that I can't
use a bare "hg push" any more, since I don't want to push the feature
branches to hg.python.org? Instead, I need to name all the branches I
want to push explicitly.

2. Once I'm done with the feature branch, I need to nuke it somehow
(e.g. by enabling the mq extension to gain access to "hg strip"
command)

If those are both accurate, I may actually create a new subclone,
leaving the main local repository with only the changes I actually
want to push upstream.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
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