From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.224.47.65 with SMTP id m1cs4635qaf; Tue, 16 Nov 2010 06:35:24 -0800 (PST) Received: by 10.231.12.130 with SMTP id x2mr3955710ibx.138.1289918122809; Tue, 16 Nov 2010 06:35:22 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id n49si3063907yha.180.2010.11.16.06.35.22; Tue, 16 Nov 2010 06:35:22 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 23E8318583BC; Tue, 16 Nov 2010 09:35:22 -0500 (EST) Received: from mail-ew0-f50.google.com (mail-ew0-f50.google.com [209.85.215.50]) by rubyforge.org (Postfix) with ESMTP id 8FC3C18583B0 for ; Tue, 16 Nov 2010 09:30:19 -0500 (EST) Received: by ewy7 with SMTP id 7so44582ewy.23 for ; Tue, 16 Nov 2010 06:30:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:subject :from:to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=kMFn5BSoT4Owmdk1OHQFN8G+HEZNfbF24mChopx6RxM=; b=iJtsxHm8hUaAks2gfPeEuTLF7wALB3Dt2LcsIeBJvZA1v442hoIMw2Ee8vZdanH4EN bxPpoL7qHaGbDO69yQfFvLUzcb/7MGnolnTWx+upNM9tB3GUZAtbsglsK5LWoZ3d41kf cODSmEkO/hjlvgt4Jt/XIeOc8h6pGrspBjKIw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=tyCDS3dgWPzPmwY12IAkNdcHVhGg091KG+SYHFX1Ti9PgGE84sZCQqBq9GgjFyPTNQ 6wveRvBDDRDrNSF9f5/JX9Yvwn52J9Knw0NKEsFvDPuhjLfd/OfkFxxBI2/0hEZ9q5qD tIa4WdG0XUghhhrKH7VCJKXQn7FaBSgik7x/k= Received: by 10.216.86.149 with SMTP id w21mr523647wee.111.1289917818318; Tue, 16 Nov 2010 06:30:18 -0800 (PST) Received: from localhost (mut38-4-82-233-117-144.fbx.proxad.net [82.233.117.144]) by mx.google.com with ESMTPS id a2sm590870wer.17.2010.11.16.06.30.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 16 Nov 2010 06:30:16 -0800 (PST) From: Damien Leone To: sup-devel In-reply-to: <1289849196-sup-128@alipc-laptop> References: <1289849196-sup-128@alipc-laptop> Date: Tue, 16 Nov 2010 15:30:14 +0100 Message-Id: <1289917099-sup-3698@mailer> User-Agent: Sup/git Subject: Re: [sup-devel] state of maildir-sync branch? X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Hello, I would say that the work is almost done, I still have things on my todo list which are: - Merge the replied/forwarded tag at the first synchronisation back to the IMAP so no information is lost - There is still some work to do on the Polling#do_poll function because the way it is in the branch is too hackish - Allow to move an email from a maildir to another - Put a special flag or file for the first time you run sup with the branch so you get asked if you want to sync everything now Beside that I have been running the branch for months without issue, just a little bug that might be related to the point 2 of the list. I often rebase the branch to master so it stays up to date, you can find this on my repository [0] in the maildir-sync-master branch. The damien branch is the same with extra patches I made months ago that have not been reviewed. Cheers, [0] : http://git.fensalir.fr/?p=dleone/sup.git;a=summary Excerpts from Ali Lown's message of lun. nov. 15 20:29:22 +0100 2010: > What happened to this branch, because it hasn't been worked on since July, but doesn't appear to have been merged into master/next. > Does anyone know what else needs to be done to get it suitable for merging (besides a git rebase)? -- Damien Leone Web: http://dleone.fensalir.fr/ GPG: 0x82EB4DDF _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel