Message184124
| 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? |
|