From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.224.216.195 with SMTP id hj3cs82649qab; Mon, 15 Nov 2010 13:10:07 -0800 (PST) Received: by 10.42.76.66 with SMTP id d2mr4966584ick.219.1289855405160; Mon, 15 Nov 2010 13:10:05 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id hd2si966881ibb.75.2010.11.15.13.10.04; Mon, 15 Nov 2010 13:10:05 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 3AC951858376; Mon, 15 Nov 2010 16:10:04 -0500 (EST) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.CMU.EDU [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id F319F18581B2 for ; Mon, 15 Nov 2010 15:53:00 -0500 (EST) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1PI62t-0005nS-Od; Mon, 15 Nov 2010 15:53:00 -0500 From: Rich Lane To: Ali Lown In-reply-to: <1289849196-sup-128@alipc-laptop> References: <1289849196-sup-128@alipc-laptop> Date: Mon, 15 Nov 2010 15:52:59 -0500 Message-Id: <1289854240-sup-7909@zyrg.net> User-Agent: Sup/git Cc: sup-devel 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 Excerpts from Ali Lown's message of Mon Nov 15 14:29:22 -0500 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)? > -Ali I'll take a look. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel