Nut upsdev - Nov 2008 - Renaming variables

I would like to rename the following variables in docs/new-names.txt:

     ambient.temperature.alarm.maximum
     ambient.temperature.alarm.minimum
     ambient.humidity.alarm.maximum
     ambient.humidity.alarm.minimum

to

     ambient.temperature.high
     ambient.temperature.low
     ambient.humidity.high
     ambient.humidity.low

The reason is that for most other variables, <maximum> and <minimum>
are used for measured/observed values (input.voltage.maximum) and  
<high> and <low> for trigger levels (battery.charge.low,  
input.transfer.high).

Any objections to this change?

Best regards, Arjen
-- 
Please keep list traffic on the list

2008/11/5 Arjen de Korte <nut+devel at
de-korte.org>:
> I would like to rename the following variables in docs/new-names.txt:
>
>     ambient.temperature.alarm.maximum
>     ambient.temperature.alarm.minimum
>     ambient.humidity.alarm.maximum
>     ambient.humidity.alarm.minimum
>
> to
>
>     ambient.temperature.high
>     ambient.temperature.low
>     ambient.humidity.high
>     ambient.humidity.low
>
> The reason is that for most other variables, <maximum> and
<minimum>
> are used for measured/observed values (input.voltage.maximum) and
> <high> and <low> for trigger levels (battery.charge.low,
> input.transfer.high).
>
> Any objections to this change?
perfect, no objection.

-- Arnaud

On Wed, Nov 5, 2008 at 5:09 PM, Arjen de Korte <nut+devel at de-korte.org>
wrote:
> I would like to rename the following variables in docs/new-names.txt:
>
>     ambient.temperature.alarm.maximum
>     ambient.temperature.alarm.minimum
>     ambient.humidity.alarm.maximum
>     ambient.humidity.alarm.minimum
>
> to
>
>     ambient.temperature.high
>     ambient.temperature.low
>     ambient.humidity.high
>     ambient.humidity.low
This is pretty much limited to the SNMP drivers, right?

-- 
- Charles Lepple