[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-libc-dev] [bug #30363] _delay_xx() functions in <util/delay.h>a

From: Boyapati, Anitha
Subject: RE: [avr-libc-dev] [bug #30363] _delay_xx() functions in <util/delay.h>are broken
Date: Tue, 15 Feb 2011 21:47:10 +0800

>-----Original Message-----
>From: Weddington, Eric
>Sent: Tuesday, February 15, 2011 7:13 PM
>To: Boyapati, Anitha; Bill Perry; Joerg Wunsch; address@hidden
>Subject: RE: [avr-libc-dev] [bug #30363] _delay_xx() functions in
><util/delay.h>are broken
>> -----Original Message-----
>> From: address@hidden
>> [mailto:address@hidden On
>> Behalf Of Anitha Boyapati
>> Sent: Monday, February 14, 2011 11:43 PM
>> To: Boyapati, Anitha; Bill Perry; Joerg Wunsch; address@hidden
>> Subject: [avr-libc-dev] [bug #30363] _delay_xx() functions in
>> <util/delay.h>are broken
>> Update of bug #30363 (project avr-libc):
>>                   Status:             In Progress => Fixed
>>          Discussion Lock:                     Any => Locked
>Hi Anitha,
>I think that we would prefer that you not lock the discussion on a bug
>unless the conversation in the bug comments have turned into some sort of
>flame war. Even if the bug is fixed, a user may come back and re-open the
>bug and they will need to make a comment.

Err..I thought all fixed and closed bugs can have locked discussions. No? I 
mean if a bug is re-opened can not the discussed be unlocked?

Actually I did not mean to lock it (changed it unintentionally and did not 
revert it back assuming it is ok) but only change the status to fixed. 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]