+2 :)
On Tue, 2010-02-16 at 19:15 +0300, Nicole Engard wrote:
> +1
>
> On Tue, Feb 16, 2010 at 11:04 AM, Chris Nighswonger
> wrote:
> > On Tue, Feb 16, 2010 at 10:50 AM, Paul Poulain
> > wrote:
> >> Le 16/02/2010 16:28, Galen Charlton a écrit :
> >>> Hi,
> >>>
> >>> I would like to have the defau
+1
On Tue, Feb 16, 2010 at 11:04 AM, Chris Nighswonger
wrote:
> On Tue, Feb 16, 2010 at 10:50 AM, Paul Poulain
> wrote:
>> Le 16/02/2010 16:28, Galen Charlton a écrit :
>>> Hi,
>>>
>>> I would like to have the default value of GranularPermissions be ON
>>> for 3.2, and push a DBrev to turn it on
On Tue, Feb 16, 2010 at 10:50 AM, Paul Poulain
wrote:
> Le 16/02/2010 16:28, Galen Charlton a écrit :
>> Hi,
>>
>> I would like to have the default value of GranularPermissions be ON
>> for 3.2, and push a DBrev to turn it on for existing installations.
>> Particularly with new_acq, I think we've
Le 16/02/2010 16:28, Galen Charlton a écrit :
> Hi,
>
> I would like to have the default value of GranularPermissions be ON
> for 3.2, and push a DBrev to turn it on for existing installations.
> Particularly with new_acq, I think we've reached to point to do this.
> Any objections?
>
sounds a v
Hi,
I would like to have the default value of GranularPermissions be ON
for 3.2, and push a DBrev to turn it on for existing installations.
Particularly with new_acq, I think we've reached to point to do this.
Any objections?
Regards,
Galen
--
Galen Charlton
gmcha...@gmail.com
_
