From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.137.132 with SMTP id w4cs80972bkt; Mon, 12 Apr 2010 02:53:24 -0700 (PDT) Received: by 10.204.132.196 with SMTP id c4mr4481790bkt.5.1271066004274; Mon, 12 Apr 2010 02:53:24 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id u10si9884481bkz.11.2010.04.12.02.53.23; Mon, 12 Apr 2010 02:53:24 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 6DB171D799C0; Mon, 12 Apr 2010 05:53:23 -0400 (EDT) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 82AA51858267 for ; Mon, 12 Apr 2010 05:53:05 -0400 (EDT) Received: by kuovi.tilus.net (Postfix, from userid 1000) id A802A6011; Mon, 12 Apr 2010 12:53:04 +0300 (EEST) From: Tero Tilus To: sup-talk In-reply-to: <1271023429-sup-9851@zyrg.net> References: <1271023429-sup-9851@zyrg.net> Date: Mon, 12 Apr 2010 12:53:04 +0300 Message-Id: <1271064967-sup-4090@tilus.net> User-Agent: Sup/git Subject: Re: [sup-talk] current state of synching upstream? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup 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-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Rich Lane, 2010-04-12 03:57: > Sup will automatically detect changes to the Seen flag in the > maildir and update the message's labels. What about Trashed, Draft and Flagged? They have obvious counterparts in Sup labels too. > I haven't decided what to do about the other direction. Historically > Sup has never modified mail sources, but changing flags in a maildir > is safe enough that I might implement it. For what I know maildir was designed to handle delivery, deletion and flag changes "safely" (no mail content corruption) even without locking. Updating message status upstream is a major point for multi-agent users. And I have got the impression that there are quire a few of them already. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk