Re: [cdt-dev] Bug id labels in cvs commits

[Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx>]

It has to be a rule. If it is the rule I am fine. I am not big fan of
lots of variations. Personally BUG 1234 looks ugly.


On Fri, Mar 11, 2011 at 3:17 PM, Sergey Prigogin
<eclipse.sprigogin@xxxxxxxxx> wrote:
>
>
> On Fri, Mar 11, 2011 at 12:07 PM, Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx>
> wrote:
>>
>> we still have people who do not understand the rule:
>> use
>> "Bug 12345 - comment"
>> format for comment in commits. How hard is that?
>
> Let me ask another question. How hard is it to make cvsgenie to use regular
> expression pattern "(.*\s|^)bug(zilla)?\s(\d+).*"?
> -sergey
>>
>> These are the recent error from cvs genie
>>
>> 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
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>