- Next message: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Previous message: Brian Barrett: "Re: problems in LAM.7, MPI.7"
- In reply to: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Next in thread: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Reply: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
Brian Barrett <brbarret_at_[hidden]>:
> Thank you. These changes have been committed (with some small
> changes) into our subversion repository and will be part of the next
> LAM release.
I'll have a few more coming. Your project has man pages in places
I did not originally check.
The immediate purpose behind these is to clean everything up so it can
be automatically lifted to XML-DocBook by a tool I wrote for the
purpose. That in turn is a means to supporting automatic generatiion
of high-quality HTML that distro integrators can use to replace
man-page trees.
To this end, I hope your "some small changes" won't involve adding
low-level troff requests back in -- .br, .ti, and .in are especially
problematic.
--
Eric S. Raymond
- Next message: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Previous message: Brian Barrett: "Re: problems in LAM.7, MPI.7"
- In reply to: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Next in thread: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Reply: Brian Barrett: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
|
