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

[Python-Dev] Hg: inter-branch workflow

[Python-Dev] Hg: inter-branch workflowBrian Curtin brian.curtin at gmail.com
Thu Mar 17 14:10:15 CET 2011
On Thu, Mar 17, 2011 at 07:41, Jesus Cea <jcea at jcea.es> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 17/03/11 13:35, Jesus Cea wrote:
> > Tonight I was thinking about doing a merge inside the branch, to solve
> > the "+1 branch". Something like transforming:
>
> Another thing I was thinking about tonight was... dropping the "+1 head"
> banning. Embrace it. Embrace the mercurial way completely.
>
> Each developer is responsible of merging HIS heads. If somebody
> "forgets", nothing wrong will happens. And no patch is left behind,
> because you can see unmerged patches with "hg heads", and bug their owners.


That just makes more work.

1. I, being new to hg, might not realize my error and just think I'm done. I
move on with life.
2. Someone has to notice the additional head then contact me.
3. Now I have to go back and figure out not only what I did wrong, but what
I have to do to correct it.

In the end, yes, it's my problem, but just because you can shoot yourself in
the foot doesn't mean we need to let people do it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20110317/b7a17b20/attachment.html>
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