Re: bugtraq:logrex documentation

On 18/04/2008, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On Fri, Apr 18, 2008 at 10:24 AM, Simon Large
> <simon.tortoisesvn_at_googlemail.com> wrote:
> > Hi folks,
> >
> > Reading through our docs on issue tracking I realise that I don't
> > really understand the description of the logregex setting. What I
> > think it is trying to say is that if you always enter issues in a
> > fixed format, eg. "Issue #123, Issue #124" then you can get away with
> > a single line regex. If you want a more natural language, eg. "Issues
> > #123, #46 and #48" then you need the first regex to extract the entire
> > issues string, and a second to extract the bug IDs from the string the
> > the first regex extracted. Is that correct?
>
>
> I would change the docs to always recommend the two-line regex. It's
> much easier to write the regex that way.
> The single-line regex is only there because some issuetrackers do use
> those (e.g., trac). But in that case, the users would have to copy the
> regex string from the issuetracker-docs anyway.

I have left it in, but after the 2-regex description and marked as not
recommended.

Out of interest I tried putting the sample single line regex in a test
WC. The log message editor picks out the issue numbers OK (matching
expression turns blue), but there is no BUG-ID column in the log
dialog. Is that expected?

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org