You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by James Peach <ja...@me.com> on 2011/12/23 09:24:26 UTC
plugin API man pages
Hi all,
I made a start on converting the v2 SDK reference pages to section 3 man pages. If this is the desired approach for reference material and they look OK on the supported OSs, I can convert a few more ...
Re: plugin API man pages
Posted by Victor Lucero <vi...@ipartner.cl>.
listo el contabilizador de errores
tomas usa la tabla salud
y usa el server dep pruebas
200.111.157.243
ser root
pass deltree
ahi esta la db con los cambios y esta reviviendo data en vivo
Saludos Cordiales.
Victor Lucero
Consultor IT
IPartner Limitada
T.(562) 6382630 C(569) 8922 9712
http://www.ipartner.cl
El 23-12-2011, a las 14:44, James Peach escribió:
> On Dec 23, 2011, at 1:40 AM, Igor Galić wrote:
>
>>
>>
>> ----- Original Message -----
>>> Hi all,
>>>
>>> I made a start on converting the v2 SDK reference pages to section 3
>>> man pages. If this is the desired approach for reference material
>>> and they look OK on the supported OSs, I can convert a few more ...
>>
>> As you can see in the new docs I dropped the SDK reference because
>> I felt it wrong to maintain reference documentation in two places.
>> To me personally an up-to-date Doxygen is more worth - I think we
>> could go from *there* to create man pages - thoughts?
>
> You could do either man <- doxygen -> html or man -> html.
>
> I haven't ever used the doxygen man page generation; google seems to have mixed feedback. I've previously used the docbook stuff and it was pretty painful. You end up having to to a lot of silly things to get the man formatting reasonable. mdoc is tedious but it's a pretty simple toolchain and easy to work from examples.
>
> I don't have a strong opinion either way, but I agree that you don't want to have to maintain documentation in 2 places. It's important that there be a strong consensus on what people are willing to maintain and contribute to.
>
> J
>
>>
>>
>>> cheers,
>>> James
>>
>> i
>>
>> --
>> Igor Galić
>>
>> Tel: +43 (0) 664 886 22 883
>> Mail: i.galic@brainsware.org
>> URL: http://brainsware.org/
>> GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
>>
>
Re: plugin API man pages
Posted by Victor Lucero <vi...@ipartner.cl>.
ups
sorry
ignere that
Saludos Cordiales.
Victor Lucero
Consultor IT
IPartner Limitada
T.(562) 6382630 C(569) 8922 9712
http://www.ipartner.cl
El 23-12-2011, a las 14:44, James Peach escribió:
> On Dec 23, 2011, at 1:40 AM, Igor Galić wrote:
>
>>
>>
>> ----- Original Message -----
>>> Hi all,
>>>
>>> I made a start on converting the v2 SDK reference pages to section 3
>>> man pages. If this is the desired approach for reference material
>>> and they look OK on the supported OSs, I can convert a few more ...
>>
>> As you can see in the new docs I dropped the SDK reference because
>> I felt it wrong to maintain reference documentation in two places.
>> To me personally an up-to-date Doxygen is more worth - I think we
>> could go from *there* to create man pages - thoughts?
>
> You could do either man <- doxygen -> html or man -> html.
>
> I haven't ever used the doxygen man page generation; google seems to have mixed feedback. I've previously used the docbook stuff and it was pretty painful. You end up having to to a lot of silly things to get the man formatting reasonable. mdoc is tedious but it's a pretty simple toolchain and easy to work from examples.
>
> I don't have a strong opinion either way, but I agree that you don't want to have to maintain documentation in 2 places. It's important that there be a strong consensus on what people are willing to maintain and contribute to.
>
> J
>
>>
>>
>>> cheers,
>>> James
>>
>> i
>>
>> --
>> Igor Galić
>>
>> Tel: +43 (0) 664 886 22 883
>> Mail: i.galic@brainsware.org
>> URL: http://brainsware.org/
>> GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
>>
>
Re: plugin API man pages
Posted by Victor Lucero <vi...@ipartner.cl>.
btw already changed the credentials
El 23-12-2011, a las 14:44, James Peach escribió:
> On Dec 23, 2011, at 1:40 AM, Igor Galić wrote:
>
>>
>>
>> ----- Original Message -----
>>> Hi all,
>>>
>>> I made a start on converting the v2 SDK reference pages to section 3
>>> man pages. If this is the desired approach for reference material
>>> and they look OK on the supported OSs, I can convert a few more ...
>>
>> As you can see in the new docs I dropped the SDK reference because
>> I felt it wrong to maintain reference documentation in two places.
>> To me personally an up-to-date Doxygen is more worth - I think we
>> could go from *there* to create man pages - thoughts?
>
> You could do either man <- doxygen -> html or man -> html.
>
> I haven't ever used the doxygen man page generation; google seems to have mixed feedback. I've previously used the docbook stuff and it was pretty painful. You end up having to to a lot of silly things to get the man formatting reasonable. mdoc is tedious but it's a pretty simple toolchain and easy to work from examples.
>
> I don't have a strong opinion either way, but I agree that you don't want to have to maintain documentation in 2 places. It's important that there be a strong consensus on what people are willing to maintain and contribute to.
>
> J
>
>>
>>
>>> cheers,
>>> James
>>
>> i
>>
>> --
>> Igor Galić
>>
>> Tel: +43 (0) 664 886 22 883
>> Mail: i.galic@brainsware.org
>> URL: http://brainsware.org/
>> GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
>>
>
Re: plugin API man pages
Posted by James Peach <ja...@me.com>.
On Dec 23, 2011, at 1:40 AM, Igor Galić wrote:
>
>
> ----- Original Message -----
>> Hi all,
>>
>> I made a start on converting the v2 SDK reference pages to section 3
>> man pages. If this is the desired approach for reference material
>> and they look OK on the supported OSs, I can convert a few more ...
>
> As you can see in the new docs I dropped the SDK reference because
> I felt it wrong to maintain reference documentation in two places.
> To me personally an up-to-date Doxygen is more worth - I think we
> could go from *there* to create man pages - thoughts?
You could do either man <- doxygen -> html or man -> html.
I haven't ever used the doxygen man page generation; google seems to have mixed feedback. I've previously used the docbook stuff and it was pretty painful. You end up having to to a lot of silly things to get the man formatting reasonable. mdoc is tedious but it's a pretty simple toolchain and easy to work from examples.
I don't have a strong opinion either way, but I agree that you don't want to have to maintain documentation in 2 places. It's important that there be a strong consensus on what people are willing to maintain and contribute to.
J
>
>
>> cheers,
>> James
>
> i
>
> --
> Igor Galić
>
> Tel: +43 (0) 664 886 22 883
> Mail: i.galic@brainsware.org
> URL: http://brainsware.org/
> GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
>
Re: plugin API man pages
Posted by Igor Galić <i....@brainsware.org>.
----- Original Message -----
> Hi all,
>
> I made a start on converting the v2 SDK reference pages to section 3
> man pages. If this is the desired approach for reference material
> and they look OK on the supported OSs, I can convert a few more ...
As you can see in the new docs I dropped the SDK reference because
I felt it wrong to maintain reference documentation in two places.
To me personally an up-to-date Doxygen is more worth - I think we
could go from *there* to create man pages - thoughts?
> cheers,
> James
i
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE