This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author chris.jerdonek
Recipients chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, pitrou, sandro.tosi, terry.reedy, tshepang
Date 2013-01-13.09:35:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358069757.88.0.0100798210217.issue14468@psf.upfronthosting.co.za>
In-reply-to
Content
I think it could cause confusion to have FAQs spread across two different files because then we'll have to distinguish between two FAQs in our hyperlinks, and it won't be obvious which FAQ page contains which questions.

I would recommend creating a new section in our existing FAQ called something like "Using Mercurial with CPython," optionally subdividing that into a committer section and an "everyone" section.  The original section can be morphed into a section answering generic questions about Mercurial (not necessarily specific to CPython or the patch workflow).

If a question is important enough to be on the same page as the rest of committing.rst, it can be added as a normal section of that page (what is the need to give all of those sections FAQ-style titles?).
History
Date User Action Args
2013-01-13 09:35:57chris.jerdoneksetrecipients: + chris.jerdonek, terry.reedy, ncoghlan, pitrou, ezio.melotti, eric.araujo, sandro.tosi, tshepang
2013-01-13 09:35:57chris.jerdoneksetmessageid: <1358069757.88.0.0100798210217.issue14468@psf.upfronthosting.co.za>
2013-01-13 09:35:57chris.jerdoneklinkissue14468 messages
2013-01-13 09:35:57chris.jerdonekcreate