Re: [sup-talk] [PATCH] minor nits in exception apology message

From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] minor nits in exception apology message
Date: Sun, 01 Nov 2009 18:49:11 +0100	[thread overview]
Message-ID: <1257097118-sup-8031@peray> (raw)
In-Reply-To: <1257096395-sup-2011@masanjin.net>

Excerpts from William Morgan's message of Sun Nov 01 18:30:04 +0100 2009:
> 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

I think some habits are needed in each model...

> b) translating a user's bug report email into an issue. :)

Yes this translating job can really be boring. In fact I consider every
bugtracker related task to be boring... And yes the nice part of web
based bugtracker is to put this burden on the user.

-- 
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk