[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] Bugzilla comments in cvs commits
|
I was kinda thinking the same. Depends on whether genie is using regex's or just regular string matching, I guess.
On Wed, Jun 2, 2010 at 9:51 AM,
<Warren.Paul@xxxxxxxxx> wrote:
I don’t know anything about the genie, but is it really that
hard for a script to check for a few different combinations? I don’t think you’ll
ever get everyone to remember and stick to this format. Even if they get an
auto-generated email, it’s still after the fact which does no good IMO.
I mean, any string containing “bug”, case-insensitive, followed
by some integer, maybe even making sure it has 5-7 digits? That would seem to cover
all ERROR’s from below.
Thanks,
Warren
On Wed, Jun 2, 2010 at 9:21 AM, Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx> wrote:
Despite my messages people still continue to use invalid
format for
bug reference in commit comment.
Please! it is not that hard! Tool cannot pick it up if it is ill
formatted.
I would suggest to Genie to send a gentle email to the offender.
Andrew
Here are example of recent commits, if you recognize yourself please
take a note:
ERROR 3: Possible invalid bug formating: "Auto indentation in calls to
template functions. Bug 314995.
ERROR 3: Possible invalid bug formating: "BUG 314055 - Updated build
files to add EDC docs manual to CDT build"
ERROR 3: Possible invalid bug formating: "Bugzilla 312098 : [Memory
Browser] do not create a rendering automatically when Memory Browser
is opened. Additional cleanup per John Cortell suggestions/issues.
ERROR 3: Possible invalid bug formating: "fix for Bug 312011 -
Helios is missing several platforms
ERROR 3: Possible invalid bug formating: "further changes for Bug
291815 - fix test failure on UNIX/Linux"
ERROR 3: Possible invalid bug formating: "This is a continuation of
Bugzilla 312098 : [Memory Browser] do not create a rendering
automatically when Memory Browser is opened. Changed the code dealing
with the Wrong _expression_ displayed to be used consistently.
ERROR 3: Possible invalid bug formating: "Workaround to get around bug
214215
Format suppose to be
Bug 123456 bug comment
(: or , can follow the bug number too)
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev