Hi Steve
You wrote:
> The reason we introduced those properties was that bugtrackers could
> parse the log messages and find the associated bug id better.
> And to do
> that, we had to define that the bug id _must_ be in a separate line
Agreed, that's nice, but not necessary.
> either at the beginning or the end of the log message.
No, that's not right. My regex for the bug tracker can find the bug-id
anywhere in the message. Restricting it to a single line makes life easier,
restricting it to beginning or end of the log message is not necessary at
all.
> Without that, you
> simply can't parse the bug id with 100% accuracy.
I don't agree here, it's just a matter of how you define your ID string. The
XML below is a perfect example of how it could be done.
> > Here is a sample log message:
> >
> > -----------------------------------------------
> > <summary>Fix crash bug</summary>
> >
> > <description>Yadda yadda yadda...</description>
> >
> > <fixes>1234</fixes>
> >
> > <qa>bob 2004/11/22 11:31</qa>
> > -----------------------------------------------
> >
> > bugtraq:message property is set to "<fixes>%BUGID%</fixes>".
>
> With those XML style log messages, it would be possible to
> really find
> the bug id even in the middle of a log message. But 'normal' log
> messages don't look like this, and so it wouldn't be possible
> to extract
> the bug id accurately.
Would you like my regex?
Cheers
-Lübbe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 17 09:23:00 2005