From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs414656agc; Sun, 1 Nov 2009 09:34:41 -0800 (PST) Received: by 10.224.114.30 with SMTP id c30mr2304870qaq.345.1257096881053; Sun, 01 Nov 2009 09:34:41 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 9si6621799qyk.27.2009.11.01.09.34.40; Sun, 01 Nov 2009 09:34:41 -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 B8BE01858282; Sun, 1 Nov 2009 12:34:40 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 2C2C618581EF for ; Sun, 1 Nov 2009 12:30:05 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N4eFg-00067n-5r for sup-talk@rubyforge.org; Sun, 01 Nov 2009 09:30:04 -0800 From: William Morgan To: sup-talk In-reply-to: <1257093429-sup-8020@peray> References: <1256749942-sup-4831@arrakis.es.net> <1256760295-sup-9873@peray> <1256760970-sup-8118@arrakis.es.net> <1256939476-sup-2864@masanjin.net> <1256987483-sup-338@tilus.net> <1257086191-sup-1136@masanjin.net> <1257088992-sup-5165@peray> <1257091305-sup-4606@masanjin.net> <1257093429-sup-8020@peray> Date: Sun, 01 Nov 2009 09:30:04 -0800 Message-Id: <1257096395-sup-2011@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] [PATCH] minor nits in exception apology message 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 Nicolas Pouillard's message of 2009-11-01: > What I found cool about distributed bugtrackers is that the > bug-closing action can follow the code that fixes the bug. Being in a > branch, or being reviewed... > > About non-technical users, I think that just a mail (thread) on the > mailing-list could suffice. Of course some web app can make things > clearer. It's funny, the two things that I found irritating do were a) close the bug as part of the commit (because I kept forgetting, and also because I like reading commits with git log -p and the ditz stuff was additional noise), and b) translating a user's bug report email into an issue. :) -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk