Message75566
| Author | amaury.forgeotdarc |
|---|---|
| Recipients | amaury.forgeotdarc, christian.heimes, severb |
| Date | 2008-11-06.16:43:13 |
| SpamBayes Score | 5.42217e-06 |
| Marked as misclassified | No |
| Message-id | <1225989797.59.0.214042609727.issue4263@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I do concur with the desire to restrict changes during RC phase. Do this also mean that merges from trunk will be reduced to the strict minimum? No global merge, only on a revision basis after review. In this case we could apply the patch to the trunk, and let a future global merge propagate the change to py3k. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-11-06 16:43:17 | amaury.forgeotdarc | set | recipients: + amaury.forgeotdarc, christian.heimes, severb |
| 2008-11-06 16:43:17 | amaury.forgeotdarc | set | messageid: <1225989797.59.0.214042609727.issue4263@psf.upfronthosting.co.za> |
| 2008-11-06 16:43:14 | amaury.forgeotdarc | link | issue4263 messages |
| 2008-11-06 16:43:13 | amaury.forgeotdarc | create | |