From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.182.180.80 with SMTP id dm16csp43417obc; Thu, 17 Jan 2013 15:01:31 -0800 (PST) X-Received: by 10.182.188.69 with SMTP id fy5mr5343659obc.74.1358463690826; Thu, 17 Jan 2013 15:01:30 -0800 (PST) Return-Path: Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com. [50.56.192.79]) by mx.google.com with ESMTP id i2si3098238oba.103.2013.01.17.15.01.27; Thu, 17 Jan 2013 15:01:30 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id F1A632E0A6; Thu, 17 Jan 2013 23:01:28 +0000 (UTC) Received: from mail-ia0-f178.google.com (mail-ia0-f178.google.com [209.85.210.178]) by rubyforge.org (Postfix) with ESMTP id 3592E2E096 for ; Thu, 17 Jan 2013 23:01:22 +0000 (UTC) Received: by mail-ia0-f178.google.com with SMTP id y26so891897iab.9 for ; Thu, 17 Jan 2013 15:01:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=daGYC4sDxXPeMadjzF/F79bIJ2dgVllklERD8nO3pOQ=; b=huWd0T4f5TR2uhPAjcF9PSVw+i3nicyk635X13gRp2OAZwx+GJqt8bCFk5RneDGRzg LH3u9IgO5moJbTCjJTSax6IfQT/F/poaSAicNvw8W/q6wsL8j6EN2I7lRP84octQuYnG 64h1fcoarJzJgLI0NdBqX/h9Kmu814/C9Ve+7uSuv9Z4j6I73zOL9jxacqp6eLy/YMRB vY63SO9u2aDef/qMp7TLdmj+4NEtZovOf6dUV0M8gSEsxRo9BsfHMPAIgiRF2w1q2Ab9 bYoNznAHJ+iREusOyqmpLhNMKnuodWVJDv1w0MDe7hxB0cLMyxERwy+gqp0CqYMV9V1n zVlw== X-Received: by 10.50.187.197 with SMTP id fu5mr339651igc.95.1358463680282; Thu, 17 Jan 2013 15:01:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.141.135 with HTTP; Thu, 17 Jan 2013 15:01:00 -0800 (PST) In-Reply-To: References: From: Hamish D Date: Thu, 17 Jan 2013 23:01:00 +0000 Message-ID: To: Matthieu Rakotojaona Cc: sup-devel Subject: Re: [sup-devel] [sup-talk] Github organization for sup and heliotrope 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org > I'm quite attracted to the git-flow [1] > model; I propose we follow it, and have therefore created a develop > branch which is just a branch at the same level as master. Please, > feel free to fork develop and code/test over it. I already have a > bunch of propositions to do and will soon put them in the repo (I just > realized my own repo was way too dirty to put it up now) I've pushed the next branch from the old sup repo to the develop branch of the new sup repo. Those are patches I'd previously reviewed and accepted. What is currently on master is what I was thinking about asking William to release as sup 0.13 but I never quite made that happen. There are various other branches in the old git repo aswell. Do we want to put them all on github for merging in our own sweet time? Or just review them locally and only push the good ones? Hamish _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel