[PATCH 00/13] Re: imaplib2/IDLE again
Sebastian at SSpaeth.de
Sat Mar 12 13:33:55 GMT 2011
On Sat, 12 Mar 2011 13:27:10 +0100, Nicolas Sebrecht <nicolas.s-dev at laposte.net> wrote:
> I'm stucked by the merge of the imaplib2¹ topic into next.
Glad you are working on that. And sorry it is hard. I will hold back any
more changes until we got that one out.
> To be honest, I think I miss knowledge of current code and the logic in
> the way both next and imaplib2 diverged. I've tried differents things
> but I can't make the result sane and robust enough to publish something.
> I see two ways to get this topic merged:
> 1) Revert conflicting patches from next.
> I guess most of my pain comes from the UIDPLUS feature. Should I revert
> a commit (not needed anymore) from next before merging imaplib2?
The UIDPLUS stuff is IMHO still needed and useful, even with
imaplib2. Do you want Etan or me to take current next and merge the
patches and offer a git branch to pull from? (Or send as patches to the list)
> 2) Rebase topic on top of next.
> Also, since imaplib2 is obviously material for next and since it
> conflicts hardly enough with next content you could rebase the topic on
> top of next and resend.
I think applying this to next makes sense. What is your opinion of
releasing another "stable" branch with what we have in next before
merging imaplib2 though?
> 1. What I call imaplib2 is the topic including patches 1-5, 11 and 12 as
> talked before in this thread. :-)
Yep, that makes sense to me.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the OfflineIMAP-project