[issue22992] Adding a git developer's guide to Mercurial to devguide

[Demian Brecht]

Demian Brecht added the comment:

I believe most points should be addressed in the updated patch. Below are responses to other comments (those not included have resulted in changes in the patch).


@Ezio:

> 4) it should be possible to use evolve instead of bookmarks, but evolve is currently still a work in progress, so I'm not sure is worth mentioning it yet;

I don't think that it's worth mentioning at this point given it's in an experimental state.

5) you said that named branches, bookmarks, and queues are all branches types in Mercurial.  Can you add a source for that?

No I can't, I was apparently completely off my face with the wording there :)

7) "Note that Mercurial doesn't have git's concept of staging, so all changes will be committed." [...]

Agreed that there are a number of solutions to this, my intention here is simply to point out a difference that developers coming from a git background will be surprised about. This one caught me a little off guard initially as I personally really like git's staging feature and bank on it at times.

@Berker:

> "a core developer" or "a contributor"?

Great point, thanks for that. My intention was to remove all merging-related operations and tailor it entirely towards contributors. I've reworded passages to make this clear and have removed all steps related to merging.

----------
Added file: http://bugs.python.org/file37367/issue22992.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22992>
_______________________________________