<br><br><div class="gmail_quote">2009/9/8 Charles Lepple <span dir="ltr"><<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, Sep 7, 2009 at 3:52 PM, Arnaud Quette<<a href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>> wrote:<br>
><br>
> 2009/9/7 Charles Lepple <<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>><br>
><br>
</div><div class="im">>> Could you provide an example of how you would use that for the man page?<br>
><br>
> in fact looking at the example shows that it's currently not possible.<br>
> ex with "usbhid-ups -L"<br>
</div>[...]<br>
<div class="im">> the manpage clearly wins the verbosity round.<br>
<br>
</div>Agreed.<br>
<div class="im"><br>
> I was also thinking about adding an option ("-I" or "-d" => driver-info) to<br>
> display the content of upsdrv_info. This seems still applicable for AUTHOR,<br>
> NAME, DESCRIPTION and possibly some more...<br>
<br>
</div>OK.<br>
<br>
Any preference as to where we put the AsciiDoc source for the man<br>
pages? It could make sense to consolidate everything under doc/ (e.g.<br>
doc/man/)<br>
</blockquote><div><br>indeed, that's what I was also thinking.<br><br>cheers,<br>Arnaud<br></div></div>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br>
<br>