From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs246547agb; Fri, 6 Nov 2009 05:48:08 -0800 (PST) Received: by 10.224.87.169 with SMTP id w41mr2413153qal.177.1257515287768; Fri, 06 Nov 2009 05:48:07 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 17si91959qyk.35.2009.11.06.05.48.07; Fri, 06 Nov 2009 05:48:07 -0800 (PST) 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 6793A3C803C; Fri, 6 Nov 2009 08:48:07 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 6F34B18582BE for ; Fri, 6 Nov 2009 08:47:51 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N6PAN-0000Oz-1v for sup-talk@rubyforge.org; Fri, 06 Nov 2009 05:47:51 -0800 From: William Morgan To: sup-talk In-reply-to: <1257476207-sup-3459@zyrg.net> References: <1256997213-sup-2725@masanjin.net> <80055d7c0911051838m855262bi93d149549de2da8c@mail.gmail.com> <1257476207-sup-3459@zyrg.net> Date: Fri, 06 Nov 2009 05:47:51 -0800 Message-Id: <1257509523-sup-3428@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] slowly catching up 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 Reformatted excerpts from Rich Lane's message of 2009-11-05: > Rather than committing directly to mainline, I'd rather keep a public > repo that I apply incoming patches to and that William can pull from. > This way I could do a lot of the first-line work and he could get a > more stable flow of patches to make releases from. That sounds good to me. I'm happy to add you to the gitorious repo, of course, but this is definitely more in line with the git lifestyle. We have a couple options on how to organize this, but I think the best would be for you to maintain one or more branches that I treat as integration branches, and periodically merge into master whenever you tell me they're ready. That's a very minimal amount of work for me. I can just merge it and forget it. The only things to be careful about in such a setup are not merging next into your branch (merging master in is fine and good to keep up with other stable changes), and not rebasing. And we will have to coordinate on releases, if nothing else so that I can make reasonable changelogs and release notes. How does that sound? > I can imagine that a lot of William's work caused by being the central > repository is reviewing the patches that get sent in. I'd like for > anyone who feels interested to read through incoming patches and comment > on them. I don't want any strict processes just yet, but I'd like to see > a couple of positive reviews (depending on the complexity of the patch, > etc) before things get merged. That would be great. Or heck, even an "I applied it and it works for me" is useful. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk