[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: dev Digest 5 Apr 2006 05:08:14 -0000 Issue 1119

From: Bernd Kuemmerlen <bkuemmer_at_gmx.net>
Date: 2006-05-05 13:16:34 CEST

dev-digest-help@tortoisesvn.tigris.org wrote:
> Re: bugtraq:logregex not working as expected
> 25339 by: Stefan Küng
> 25342 by: Sven Brueggemann
> Subject:
> Re: bugtraq:logregex not working as expected
> From:
> Sven Brueggemann <SBrueggemann@gmx.net>
> Date:
> Mon, 3 Apr 2006 21:27:24 +0200
> To:
> dev@tortoisesvn.tigris.org
> I understood from the docs that bugtraq:message was for inserting the
> bug id into the log message, and bugtrack:logregex for extracting
> it from a log message to pass it over to a bugtraq:url.
> Nevertheless, I think it's good to be able to have both properties
> set: One for conveniently adding bug ids at the top or bottom of
> the log message and one for gathering issues from all over the message.
>> You should remove the bugtraq:message property.
> But then the bug id field in the commit dialog will be gone, won't it?

I would like to second the request to have the ability to specify both
bugtraq:message as well as bugtraq:logregex, because of the reasons Sven
described. The Bug-ID field is very convenient, but for "mental
backwards compatibility" reasons, I would like to also support the
regexp-entry (especially because we allow different formats).

Thanks for considering.

All the best

"The first discovery I'd like to present here is an algorithm for lazy
evaluation of research papers. Just write whatever you want and don't
cite any previous work, and indignant readers will send you references
to all the papers you should have cited."              -- Paul Graham
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri May 5 13:16:50 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.