Hello,

another case. Every user use [PATCH] if he send a patch to the mailinglist. Why 
we should not use
[REVIEW] for the gerrit messages?

[Openocd-development] [PATCH] cfi: unsupported code paths are now covered by 
asserts
[Openocd-development] [REVIEW] cfi: unsupported code paths are now covered by 
asserts



Regards,

Mathias


Am 28.10.2011 20:03, schrieb Mathias K.:
> Hello,
> 
> can you remove the magic incomplete number too?
> 
> In this case the "1533d9d". This number is useless in the subject:
> 
> [Openocd-development] openocd patch: 1533d9d cfi: unsupported code paths are 
> now covered by asserts
> 
> Now we have 2 times openocd as static text left. Do you think we need it?
> 
> 
> Regards,
> 
> Mathias
> 
> 
> 
> Am 28.10.2011 16:14, schrieb Peter Stuge:
>> Jon Povey wrote:
>>>> is there any chance to reduce the gerrit subject line to a
>>>> normal length with more information at
>>>> the beginning? Currently the subject consist of 50% static text
>>>> at the beginning.
>>>>
>>>> [Openocd-development] New patch to review for openocd: XXXXXXX bugfixes:
>>>
>>> I agree. maybe one or two characters of the commit-id are all I see
>>> before the subject gets chopped off on my display.
>>
>> I just changed it to New openocd patch: xxx
>>
>>
>>> In fact I would get rid of [Openocd-development] too.
>>
>> +1 but since this is a bit more established maybe give people time to
>> change their filters? Or just change it and people will change after?
>>
>>
>> //Peter
>> _______________________________________________
>> Openocd-development mailing list
>> Openocd-development@lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/openocd-development
> 
> _______________________________________________
> Openocd-development mailing list
> Openocd-development@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/openocd-development

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to