Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Date: Fri, 28 Jan 2005 12:19:45 +0100
From: =?ISO-8859-1?Q?Andr=E9?= Malo <nd@perlig.de>
To: dev@apr.apache.org
Subject: Re: Commit mail subject lines [was: svn commit: r126493 -
 /apr/site/trunk/docs/download.html ...]
Message-ID: <20050128121945.0000001c@int.cinetic.de>
In-Reply-To: <41FA1C6F.7020400@webthing.com>
References: <20050126094736.3272.qmail@minotaur.apache.org>
	<1106868055.2958.197.camel@bashful.x10sys.com>
	<41F97ACA.10001@btopenworld.com>
	<479520065E302548D8592B7D@st-augustin.ics.uci.edu>
	<41FA1C6F.7020400@webthing.com>
Organization: TIMTOWTDI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

* Nick Kew <nick@webthing.com> wrote:

> Justin Erenkrantz wrote:
> 
> > <julianfoad@btopenworld.com> wrote:
> > 
> >> Hmm.  My thought is that the prefix "svn commit " is redundant and
should
> >> be dropped.  A subject starting with "r126493 -
> > 
> > We always had the 'cvs commit' prefix.  I see no compelling reason to
> > change this.  -- justin
> 
> I do.  It becomes much harder to track which changes are of interest
> to me when I can't see any meaningful information in the subject line.
> It's the same problem as spam: the commits I want to look at are drowned
> in those I have no interest in (e.g. recently LDAP - glad to see it
> there, but I have nothing to contribute to that work).

I find the prefix is especially useful, when someone replies to such
mails to another mailinglist (like this thread).

nd