Brett Cannon added the comment:
With the pending migration to git, this probably isn't worth the effort.
--
nosy: +brett.cannon
resolution: -> out of date
status: open -> closed
___
Python tracker
Changes by Carol Willing willi...@willingconsulting.com:
--
assignee: - willingc
nosy: +willingc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16931
___
Ezio Melotti added the comment:
This can be in a general Mercurial section before the section specific
to committers, or else spread throughout (e.g. in the FAQ).
FWIW I'm leaning towards making the committing.rst page for committers only,
and move general instructions for non-committers
Chris Jerdonek added the comment:
AFAICT, the recommendation to use hg git format is currently only mentioned
in the Committing section
(http://docs.python.org/devguide/committing.html#minimal-configuration) but
not elsewhere, in particular, not http://docs.python.org/devguide/patch.html.
Ned Deily added the comment:
However this is resolved, the information in the devguide should be consistent.
AFAICT, the recommendation to use hg git format is currently only mentioned
in the Committing section
(http://docs.python.org/devguide/committing.html#minimal-configuration) but not
New submission from Chris Jerdonek:
This issue is to mention in the devguide how to create diffs with the changeset
number when --git is configured on. Perhaps this can be done via a FAQ like:
How can I get Rietveld to work with a 2.7 patch?
Background: Currently, the devguide recommends
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16931
___
___