Re:adopting commented examples in config files

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Re:adopting commented examples in config files

mrisaliti@libero.it
Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
Is it something to commit also in the relase 4 ?

Thanks
Marco

> I like the way the Apache httpd server has it config files commented.
> it give you a example of what should go into the config.
> I user the paypal config as an example.
>
> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
> payment.paypal.notify=
>
> so the configuration person does not have to hunt down documentation
> when implementing these not so apparent configurations.
>
>

Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

BJ Freeman
I will create a general JIra for a config information
I don't have commit privileges.


[hidden email] sent the following on 12/17/2007 7:16 AM:

> Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
> Is it something to commit also in the relase 4 ?
>
> Thanks
> Marco
>
>> I like the way the Apache httpd server has it config files commented.
>> it give you a example of what should go into the config.
>> I user the paypal config as an example.
>>
>> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
>> payment.paypal.notify=
>>
>> so the configuration person does not have to hunt down documentation
>> when implementing these not so apparent configurations.
>>
>>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

Jacques Le Roux
Administrator
BJ,

Don't worry about a Jira issue (except if you see some kind of generalisation). I will commit it directly soon...

Thanks

Jacques

De : "BJ Freeman" <[hidden email]>

> I will create a general JIra for a config information
> I don't have commit privileges.
>
>
> [hidden email] sent the following on 12/17/2007 7:16 AM:
> > Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
> > Is it something to commit also in the relase 4 ?
> >
> > Thanks
> > Marco
> >
> >> I like the way the Apache httpd server has it config files commented.
> >> it give you a example of what should go into the config.
> >> I user the paypal config as an example.
> >>
> >> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
> >> payment.paypal.notify=
> >>
> >> so the configuration person does not have to hunt down documentation
> >> when implementing these not so apparent configurations.
> >>
> >>
> >
> >
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

BJ Freeman
The generalization is if we adopted the blank parm to check for, any
parm example will be lost.
so when this is done, the parm that was there should be commented then a
new parm that is blank be used.


Jacques Le Roux sent the following on 12/17/2007 10:52 AM:

> BJ,
>
> Don't worry about a Jira issue (except if you see some kind of generalisation). I will commit it directly soon...
>
> Thanks
>
> Jacques
>
> De : "BJ Freeman" <[hidden email]>
>> I will create a general JIra for a config information
>> I don't have commit privileges.
>>
>>
>> [hidden email] sent the following on 12/17/2007 7:16 AM:
>>> Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
>>> Is it something to commit also in the relase 4 ?
>>>
>>> Thanks
>>> Marco
>>>
>>>> I like the way the Apache httpd server has it config files commented.
>>>> it give you a example of what should go into the config.
>>>> I user the paypal config as an example.
>>>>
>>>> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
>>>> payment.paypal.notify=
>>>>
>>>> so the configuration person does not have to hunt down documentation
>>>> when implementing these not so apparent configurations.
>>>>
>>>>
>>>
>>>
>>>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

Jacques Le Roux
Administrator
Yes, I already agreed, see my msg from 17/12/2007 at 01:30 in this thread :o)

Doing it right now, and I will backport to release4.0

Jacques

De : "BJ Freeman" <[hidden email]>

> The generalization is if we adopted the blank parm to check for, any
> parm example will be lost.
> so when this is done, the parm that was there should be commented then a
> new parm that is blank be used.
>
>
> Jacques Le Roux sent the following on 12/17/2007 10:52 AM:
> > BJ,
> >
> > Don't worry about a Jira issue (except if you see some kind of generalisation). I will commit it directly soon...
> >
> > Thanks
> >
> > Jacques
> >
> > De : "BJ Freeman" <[hidden email]>
> >> I will create a general JIra for a config information
> >> I don't have commit privileges.
> >>
> >>
> >> [hidden email] sent the following on 12/17/2007 7:16 AM:
> >>> Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
> >>> Is it something to commit also in the relase 4 ?
> >>>
> >>> Thanks
> >>> Marco
> >>>
> >>>> I like the way the Apache httpd server has it config files commented.
> >>>> it give you a example of what should go into the config.
> >>>> I user the paypal config as an example.
> >>>>
> >>>> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
> >>>> payment.paypal.notify=
> >>>>
> >>>> so the configuration person does not have to hunt down documentation
> >>>> when implementing these not so apparent configurations.
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

BJ Freeman
don't see that message.
I am aware I don't get all the message from the ML.
considering the server my mail server is on, I am not sure why that is
the case

Jacques Le Roux sent the following on 12/17/2007 12:16 PM:

> Yes, I already agreed, see my msg from 17/12/2007 at 01:30 in this thread :o)
>
> Doing it right now, and I will backport to release4.0
>
> Jacques
>
> De : "BJ Freeman" <[hidden email]>
>> The generalization is if we adopted the blank parm to check for, any
>> parm example will be lost.
>> so when this is done, the parm that was there should be commented then a
>> new parm that is blank be used.
>>
>>
>> Jacques Le Roux sent the following on 12/17/2007 10:52 AM:
>>> BJ,
>>>
>>> Don't worry about a Jira issue (except if you see some kind of generalisation). I will commit it directly soon...
>>>
>>> Thanks
>>>
>>> Jacques
>>>
>>> De : "BJ Freeman" <[hidden email]>
>>>> I will create a general JIra for a config information
>>>> I don't have commit privileges.
>>>>
>>>>
>>>> [hidden email] sent the following on 12/17/2007 7:16 AM:
>>>>> Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
>>>>> Is it something to commit also in the relase 4 ?
>>>>>
>>>>> Thanks
>>>>> Marco
>>>>>
>>>>>> I like the way the Apache httpd server has it config files commented.
>>>>>> it give you a example of what should go into the config.
>>>>>> I user the paypal config as an example.
>>>>>>
>>>>>> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
>>>>>> payment.paypal.notify=
>>>>>>
>>>>>> so the configuration person does not have to hunt down documentation
>>>>>> when implementing these not so apparent configurations.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

Jacques Le Roux
Administrator
Anyway it's one in trunk and release4.0, following your suggestion.

Jacques

De : "BJ Freeman" <[hidden email]>

> don't see that message.
> I am aware I don't get all the message from the ML.
> considering the server my mail server is on, I am not sure why that is
> the case
>
> Jacques Le Roux sent the following on 12/17/2007 12:16 PM:
> > Yes, I already agreed, see my msg from 17/12/2007 at 01:30 in this thread :o)
> >
> > Doing it right now, and I will backport to release4.0
> >
> > Jacques
> >
> > De : "BJ Freeman" <[hidden email]>
> >> The generalization is if we adopted the blank parm to check for, any
> >> parm example will be lost.
> >> so when this is done, the parm that was there should be commented then a
> >> new parm that is blank be used.
> >>
> >>
> >> Jacques Le Roux sent the following on 12/17/2007 10:52 AM:
> >>> BJ,
> >>>
> >>> Don't worry about a Jira issue (except if you see some kind of generalisation). I will commit it directly soon...
> >>>
> >>> Thanks
> >>>
> >>> Jacques
> >>>
> >>> De : "BJ Freeman" <[hidden email]>
> >>>> I will create a general JIra for a config information
> >>>> I don't have commit privileges.
> >>>>
> >>>>
> >>>> [hidden email] sent the following on 12/17/2007 7:16 AM:
> >>>>> Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
> >>>>> Is it something to commit also in the relase 4 ?
> >>>>>
> >>>>> Thanks
> >>>>> Marco
> >>>>>
> >>>>>> I like the way the Apache httpd server has it config files commented.
> >>>>>> it give you a example of what should go into the config.
> >>>>>> I user the paypal config as an example.
> >>>>>>
> >>>>>> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
> >>>>>> payment.paypal.notify=
> >>>>>>
> >>>>>> so the configuration person does not have to hunt down documentation
> >>>>>> when implementing these not so apparent configurations.
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

mrisaliti@libero.it
In reply to this post by mrisaliti@libero.it
Sorry BJ Freeman, I'm thinking that you were a committer.
So, we can wait that someone else express ideas on what you have proposed.

Thanks
Marco

> BJ,
>
> Don't worry about a Jira issue (except if you see some kind of generalisation). I will commit it directly soon...
>
> Thanks
>
> Jacques
>
> De : "BJ Freeman" <[hidden email]>
> > I will create a general JIra for a config information
> > I don't have commit privileges.
> >
> >
> > [hidden email] sent the following on 12/17/2007 7:16 AM:
> > > Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
> > > Is it something to commit also in the relase 4 ?
> > >
> > > Thanks
> > > Marco
> > >
> > >> I like the way the Apache httpd server has it config files commented.
> > >> it give you a example of what should go into the config.
> > >> I user the paypal config as an example.
> > >>
> > >> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
> > >> payment.paypal.notify=
> > >>
> > >> so the configuration person does not have to hunt down documentation
> > >> when implementing these not so apparent configurations.
> > >>
> > >>
> > >
> > >
> > >
> > >
> >
>

Reply | Threaded
Open this post in threaded view
|

Re: adopting commented examples in config files

BJ Freeman
I am use to that
:)

[hidden email] sent the following on 12/18/2007 1:00 AM:

> Sorry BJ Freeman, I'm thinking that you were a committer.
> So, we can wait that someone else express ideas on what you have proposed.
>
> Thanks
> Marco
>
>> BJ,
>>
>> Don't worry about a Jira issue (except if you see some kind of generalisation). I will commit it directly soon...
>>
>> Thanks
>>
>> Jacques
>>
>> De : "BJ Freeman" <[hidden email]>
>>> I will create a general JIra for a config information
>>> I don't have commit privileges.
>>>
>>>
>>> [hidden email] sent the following on 12/17/2007 7:16 AM:
>>>> Yes, BJ Freeman you can commit by yourself or at least I will wait some ideas about that from others people.
>>>> Is it something to commit also in the relase 4 ?
>>>>
>>>> Thanks
>>>> Marco
>>>>
>>>>> I like the way the Apache httpd server has it config files commented.
>>>>> it give you a example of what should go into the config.
>>>>> I user the paypal config as an example.
>>>>>
>>>>> #payment.paypal.notify=http://[yourserver]/ecommerce/control/payPalNotify
>>>>> payment.paypal.notify=
>>>>>
>>>>> so the configuration person does not have to hunt down documentation
>>>>> when implementing these not so apparent configurations.
>>>>>
>>>>>
>>>>
>>>>
>>>>
>
>
>
>