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

[Python-Dev] Backport troubles with mercurial

[Python-Dev] Backport troubles with mercurial [Python-Dev] Backport troubles with mercurialAmaury Forgeot d'Arc amauryfa at gmail.com
Wed Dec 29 16:05:40 CET 2010
2010/12/29 Georg Brandl <g.brandl at gmx.net>:
>>> A change can of course also be transplanted after the fact.  It requires another
>>> merge, but usually a trivial one.
>>
>> No, it's not trivial with hg: this is the very subject of the thread!
>
> I don't understand: if you make the same change in two branches, but
> in different changesets, and then merge these branches, Mercurial will
> usually notice that and not trouble you with conflicts.

Actually I never passed the first step: make the same change to two branches.

-- 
Amaury Forgeot d'Arc
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