SteveKing <firstname.lastname@example.org> wrote on 02/11/2005 01:16:10 PM:
> Mark Phippard wrote:
> > I think I was the original person to suggest using RegEx, although
> > the idea has "morphed" into other areas.
> You were the first one, yes. But by far not the only one ;)
I just meant that I could clearly tell you were talking about something
different and I wasn't sure what.
> People requested TSVN to extract certain strings from a log message and
> turn it into a link. Also, some tools like trac
> (http://projects.edgewall.com/trac/) can even parse a log message for
> strings like
> Changed blah and foo to do this or that. Fixes #10 and #12,
> and refs #12.
> This will close #10 and #12, and add a note to #12.
> and close/fix/reference/add note to the mentioned issue (called 'ticket'
> So the regex would be used to extract the bug ID's from a log message as
> trac does it and turn them into links. And of course while we have that
> regex defined it can also be used to check the validity of an entered
> bug ID.
> Kind of like an enhancement to the current specs.
So this will all be new stuff in the specs, and all of the current stuff
will continue to work?
In fairness to you, Trac does have it a bit easier in that they only have
to support their own system and ID's. They probably do not need to do
anything other than search for # and turn numbers following it into a
link. Since it is their own system, they can even verify a number is
valid before doing so.
I still think the feature is potentially good in that it can "unleash" log
messages that were written prior to the new integration features.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Feb 11 19:51:26 2005