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 baikie
Recipients Jim.Jewett, ajaksu2, akuchling, baikie, barry, loewis, nnorwitz, peter.ll, petri.lehtinen, r.david.murray, terry.reedy
Date 2014-05-01.18:11:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20140501181040.GA1993@localhost>
In-reply-to <1398697976.28.0.295022386502.issue1599254@psf.upfronthosting.co.za>
Content
On Mon 28 Apr 2014, Jim Jewett wrote:
> pinging David Watson:  What is the status?  If I understand correctly, (and I may well not), you have already opened other issues for parts of this, and (only) the final patch is ready for patch (and hopefully) commit review.  Is this correct?

No, I haven't opened any separate issues (I would be perfectly
happy with fixing the original renaming-vs-copying problem and
then leaving this issue open to deal with the rest).  The patches
mailbox-copy-back-2.7.diff and
mailbox-tests-2.7-part1-for-copy-back.diff are what I suggest
applying for the renaming-vs-copying problem.

I haven't looked at the other patches in much detail, but for
what it's worth, the tests in mailbox-tests-2.7-part2.diff do
pass with mailbox-update-toc-again.diff applied.
History
Date User Action Args
2014-05-01 18:11:38baikiesetrecipients: + baikie, loewis, barry, akuchling, nnorwitz, terry.reedy, ajaksu2, peter.ll, r.david.murray, petri.lehtinen, Jim.Jewett
2014-05-01 18:11:37baikielinkissue1599254 messages
2014-05-01 18:11:36baikiecreate