Message130950
| Author | Trundle |
|---|---|
| Recipients | Trundle, belopolsky, brett.cannon, cool-RR, giampaolo.rodola, gruszczy, loewis, nedbat, r.david.murray, techtonik, vstinner |
| Date | 2011-03-15.03:58:52 |
| SpamBayes Score | 2.2956643e-05 |
| Marked as misclassified | No |
| Message-id | <AANLkTinNu_OamT-u2Rt6O6L6EeUdGOjVYpmZYNm2Seoy@mail.gmail.com> |
| In-reply-to | <1299498559.18.0.816626930459.issue1559549@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> I am sorry again for those mistakes, it's all completely new to me. No worries! >I have fixed those issues and created new patch. Using hg export, that now spans over two commits. Is it the way those patches should be provided, or should I gather all changes into a one commit? A single patch (where all changesets are flattened into one) is the preferred way. For general advice, you can read the Developer's Guide at http://docs.python.org/devguide/ (e.g. http://docs.python.org/devguide/patch.html). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-03-15 03:58:53 | Trundle | set | recipients: + Trundle, loewis, brett.cannon, belopolsky, vstinner, techtonik, giampaolo.rodola, nedbat, r.david.murray, gruszczy, cool-RR |
| 2011-03-15 03:58:52 | Trundle | link | issue1559549 messages |
| 2011-03-15 03:58:52 | Trundle | create | |