From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.90.87.14 with SMTP id k14cs1189400agb;
        Tue, 29 Dec 2009 12:14:48 -0800 (PST)
Received: by 10.224.78.163 with SMTP id l35mr8204499qak.347.1262117688337;
        Tue, 29 Dec 2009 12:14:48 -0800 (PST)
Return-Path: <sup-devel-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 30si20118446qyk.33.2009.12.29.12.14.48;
        Tue, 29 Dec 2009 12:14:48 -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 F36F515B802D;
	Tue, 29 Dec 2009 15:14:47 -0500 (EST)
Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168])
	by rubyforge.org (Postfix) with ESMTP id AF0E015B8029
	for <sup-devel@rubyforge.org>; Tue, 29 Dec 2009 15:14:45 -0500 (EST)
Received: by kuovi.tilus.net (Postfix, from userid 1000)
	id 1FCA33FCCC; Tue, 29 Dec 2009 22:14:45 +0200 (EET)
From: Tero Tilus <tero@tilus.net>
To: sup-devel <sup-devel@rubyforge.org>
In-reply-to: <1262116690-sup-8655@masanjin.net>
References: <1262114695-sup-9446@tilus.net> <1262116690-sup-8655@masanjin.net>
Date: Tue, 29 Dec 2009 22:14:45 +0200
Message-Id: <1262117270-sup-1009@tilus.net>
User-Agent: Sup/git
Subject: Re: [sup-devel] What's your workflow?
X-BeenThere: sup-devel@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sup developer discussion <sup-devel@rubyforge.org>
List-Id: Sup developer discussion <sup-devel.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-devel>
List-Post: <mailto:sup-devel@rubyforge.org>
List-Help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=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

William Morgan, 2009-12-29 21:58:
> See http://sup.rubyforge.org/wiki/wiki.pl?Contributing

Believe me, I have.  That's pretty much why I got this far in the
first place.  ;)

Wiki page just doesn't say anything on how to have your own daily-sup
branch (master or next + a set of own and others' patches) and how to
keep that up-to-date with upstream while your develop your own patches
(which are supposed to live in topic branches).

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel