similar to: [nut-commits] svn commit r2147 - branches/AsciiDoc/docs/man

On Mon, Sep 14, 2009 at 4:49 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Mon Sep 14 20:49:59 2009 > New Revision: 1986 > > Log: > draft index of manual pages > > Added: > branches/AsciiDoc/docs/man/index.txt Cool! One potential issue: /sw/bin/asciidoc --backend=xhtml11 \ --attribute localdate=`TZ=UTC date +%Y-%m-%d` \

On Jul 13, 2010, at 6:59 PM, Arnaud Quette wrote: > Author: aquette > Date: Tue Jul 13 22:59:52 2010 > New Revision: 2472 > URL: http://trac.networkupstools.org/projects/nut/changeset/2472 [...] > Modified: branches/AsciiDoc/docs/Makefile.am > = > = > = > = > = > = > = > = > ====================================================================== > ---

Arnaud, Thanks for removing the warning. I suspect that many users still using IE6 are doing so because of their IT department (rather than personal preference). IMHO, browser evangelism is slightly outside the scope of the NUT project :-) On Thu, Sep 3, 2009 at 8:31 AM, Arnaud Quette<aquette at alioth.debian.org> wrote: > Author: aquette > Date: Thu Sep 3 12:31:10 2009 > New

2010/11/4 Arjen de Korte > Author: adkorte-guest > Date: Thu Nov 4 22:40:51 2010 > New Revision: 2671 > URL: http://trac.networkupstools.org/projects/nut/changeset/2671 > > Log: > Exclude -I. and extra developer warning flags with Net-SNMP support enabled > (using them is the responsibility of the NUT developers) > > Modified: >

On Nov 4, 2010, at 6:21 PM, Arjen de Korte wrote: > Author: adkorte-guest > Date: Thu Nov 4 22:21:51 2010 > New Revision: 2669 > URL: http://trac.networkupstools.org/projects/nut/changeset/2669 > > Log: > Add checking minimum required version for AsciiDoc tools I noticed that somewhere around this commit, the documentation stopped being built by default in BuildBot.

On Sep 8, 2009, at 8:30 AM, Charles Lepple wrote: [...] > +EXTRA_DIST = tripplite_usb.8.txt \ > + ups.conf.5.txt \ > + upsc.8.txt > + The EXTRA_DIST thing is a hack. Right now, we are not including the generated HTML properly, because I haven't figured out the automake way to do this correctly. Specifically, we want to treat the .txt files as source, and distribute the

I'm looking for a little bit of help with the man page conversion. So far, about a third of the man pages are converted, and I think it would make sense to have a second or third set of eyes compare the output to be sure that we are not losing any information in the conversion process. In the tarballs generated from the AsciiDoc branch on http://buildbot.ghz.cc/public/nut/ you will find the

I would like to learn AsciiDoc. Is there any good examples how to use AsciiDoc with R? I know that there is packages called ascii to do this, but it would be nice to see some examples how AsciiDoc works with R. Is there an AsciiDoc distribution for Max OS X? -Johannes

Since I've heard about AsciiDoc (thanks ESR), I'm in the process of revamping the full Network UPS Tools documentation and website. Without going into the usual "it curred my desease, got my wife back home, and made me won a billion", it really saved my life ^_ ^ I was searching for such tool for years! thanks a lot Stuart and others. Kudos for the work! NUT revamp is not yet

I need to install asciidoc on my build machine. There is a version for CentOS-5 available at dags rpm site. I have a repository configured for dag like so: [dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/ baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag gpgkey=http://dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt

FYI (mostly Charles and Arjen), a2x version has just been bumped to 8.6.3 in their trunk. So we will be able revert r2686 cheers, Arno 2010/11/12 Stuart Rackham > > > On 12/11/10 10:45, Arnaud Quette wrote: > >> Hi Stuart, >> >> 2010/11/10 Stuart Rackham >> >> The planned 28-Oct release date has slipped by, in the mean time I >> think all

Hello, I'm starting to think that converting the Syslinux documentation to asciidoc would be the best, and probably easiest, way to get some kind of consistency between the web docs and what is shipped. I don't think it would be all that hard to do (see http://www.methods.co.nz/asciidoc/). Anyone interested in trying to tackle this? -hpa

On Jun 23, 2017, at 10:28 PM, Manuel Wolfshant wrote: > > Unfortunately they do not include any man pages, I did not have time to find a workaround for the hard requirement of newer versions for the tools used by the build process to create the man pages. You have mentioned the man pages several times, and I am slightly confused. If I grab a tarball from

On Aug 14, 2009, at 8:31 AM, Charles Lepple wrote: > Author: clepple-guest > Date: Fri Aug 14 12:31:25 2009 > New Revision: 1931 > > Log: > Warn when making 'html' without asciidoc tool Heh. Now I get a warning when running automake (with or without asciidoc). I'll fix that later.

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Author: aquette > Date: Sat Dec 11 12:31:21 2010 > New Revision: 2731 > URL: http://trac.networkupstools.org/projects/nut/changeset/2731 > > Log: > Complete the list of Subversion ignored files, with AsciiDoc > generated contents (no functional changes) Is there a particular reason for having both the man/

The following changes since commit ddb10ce99c327888ade4d2ba3e4c50ad12aaa059: Matt Fleming (1): Delete 16-bit COMBOOT support are available in the git repository at: git://github.com/geneC/syslinux.git doc-elflink-for-mfleming Gene Cumm (3): txt/: Add new AsciiDoc formatted documentation Makefile: add txt/ NEWS: add txt/ Makefile | 2 +- NEWS

It looks like there was an issue with the AsciiDoc merge from the trunk: http://buildbot.networkupstools.org/private/nut/builders/Ubuntu-lucid-x86/builds/119/steps/compile/logs/stdio As mentioned in the email about windows_port, I would recommend testing the branch after a merge from the trunk. You can either run "make distcheck", or contact me (off-list) to set up a password so

With the AsciiDoc conversion underway, I am wondering if we should keep the AsciiDoc for the driver man pages in a specially-formatted comment in the driver (taking a cue from the comments specifying USB information). I have been doing something similar with the tripplite_usb driver for a while - it contains Perl-style POD (Plain Old Documentation) in a C comment, and the man page can be

On Fri, 2011-12-09 at 03:46 +0000, Charles Lepple wrote: > Author: clepple-guest > Date: Fri Dec 9 03:46:11 2011 > New Revision: 3344 > URL: http://trac.networkupstools.org/projects/nut/changeset/3344 > > Log: > Force files to be overwritten (especially for libtool) > > Modified: > branches/nut-scanner_dlopen/autogen.sh > > Modified:

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what