From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs35093icb; Thu, 27 Jan 2011 22:30:29 -0800 (PST) Received: by 10.229.181.9 with SMTP id bw9mr2393375qcb.143.1296196228698; Thu, 27 Jan 2011 22:30:28 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id r23si20978889vbn.83.2011.01.27.22.30.28; Thu, 27 Jan 2011 22:30:28 -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 0FF8F1858390; Fri, 28 Jan 2011 01:30:28 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id B04131858390 for ; Fri, 28 Jan 2011 01:20:56 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1PihhX-0007gj-HU for sup-devel@rubyforge.org; Fri, 28 Jan 2011 01:20:55 -0500 From: William Morgan To: sup-devel In-reply-to: <1296112974-sup-5821@tilus.net> References: <1295894044-sup-7965@masanjin.net> <1295896722-sup-5870@midna.zekjur.net> <1296054871-sup-9586@masanjin.net> <1296112974-sup-5821@tilus.net> Date: Fri, 28 Jan 2011 01:20:50 -0500 Message-Id: <1296195497-sup-1700@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] call for new maintainers 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 Reformatted excerpts from Tero Tilus's message of 2011-01-27: > I'm http://gitorious.org/~terotil Added! And now I can ignore all your outstanding patch requests. :) > > All I ask is that you divide things into nice topic branches and > > merge them into next but not master. > > Do you prefer basing feature branches to master or next? Base them off of master, please. If they're based off of next, I can't merge them into master without also merging all of next. > Should we prefix feature branch names to keep `git branch` more > readable? They could be topic-* or feature-* or alike. I don't think that's necessary. The only two integration branches are master and next (and the release-* branches, I suppose). When I merge things into master I will delete the remote branches as well, so we shouldn't end up with a big mess. -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel