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 terry.reedy
Recipients chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, ned.deily, pitrou, python-dev, sandro.tosi, terry.reedy, tshepang
Date 2013-03-14.01:25:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1363224322.28.0.799990481995.issue14468@psf.upfronthosting.co.za>
In-reply-to
Content
For the null merge entry, /filed/files/.

The "create new remote heads". is really needed. I handled a situation wrong again today. Question: commit to 3.2, merge forward without change, push, and message is '... new remote head in 3.2'. Is 3.2 really the only branch with a head conflict? Or would one appear in 3.3 as soon as 3.2 heads are merged and merge is merged forward to 3.3?
History
Date User Action Args
2013-03-14 01:25:22terry.reedysetrecipients: + terry.reedy, ncoghlan, pitrou, ned.deily, ezio.melotti, eric.araujo, sandro.tosi, chris.jerdonek, tshepang, python-dev
2013-03-14 01:25:22terry.reedysetmessageid: <1363224322.28.0.799990481995.issue14468@psf.upfronthosting.co.za>
2013-03-14 01:25:22terry.reedylinkissue14468 messages
2013-03-14 01:25:22terry.reedycreate