Carol Willing added the comment:
I've reviewed this issue at the PyCon sprint. While I agree that there are
sections that new contributors might wish to skip over, I believe that there is
content that would benefit contributors that are not yet core developers.
Going forward we can try to
Chris Jerdonek added the comment:
Currently the section covers all the fundamental Mercurial-related operations
that a committers needs to know (set up, commit, merge, push), not just
committing.
The point of the change in section title is to have a title so non-committers
know they can
Ezio Melotti added the comment:
The point of the change in section title is to have a title so
non-committers know they can skip over the section.
In the first part of committing.rst there are also things for committers only,
and some of the content of the working with mercurial might be
Chris Jerdonek added the comment:
I think making the sections more focused helps because sections are the
linkable units, and sections can be freely moved around once they are more
stand-alone (e.g. into or out of the FAQ).
In issue 16931 in response to Ned, I suggested adding a general
Ezio Melotti added the comment:
The problem with that is that you have to navigate through different
links/pages/sections though (see also msg182645).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17284
Ezio Melotti added the comment:
This has now been committed as part of #14468.
Regarding the change of the section title, I'm not sure that's necessary.
Currently the section covers all the fundamental Mercurial-related operations
that a committers needs to know (set up, commit, merge, push),
New submission from Chris Jerdonek:
As discussed in issue 14468, this issue is to reorder the sections in the
devguide's committing.rst to create a section dedicated to using Mercurial when
committing. The attached patch is adapted from the 2-move_two_sections.diff
patch of that issue.
