svn commit: r284198 - head/bin/ls

Steve Kargl sgk at troutmask.apl.washington.edu
Sun Jun 14 06:09:41 UTC 2015


On Sat, Jun 13, 2015 at 06:45:57PM -0700, Craig Rodrigues wrote:
> On Sat, Jun 13, 2015 at 6:29 PM, Steve Kargl <
> sgk at troutmask.apl.washington.edu> wrote:
> 
> > >
> > > Are you talking about this comment you made?
> > >
> > https://lists.freebsd.org/pipermail/freebsd-current/2015-March/054899.html
> > >
> > > I can't make heads or tails of what you wrote, other than you seemed very
> > > angry.
> > >
> >
> > I wasn't very angry.
> 
> It's hard for me to tell, really, since you submitted patches
> with FUBAR in them, so you seemed pretty angry in that e-mail.
> 

FUBAR is as good as what is already there.  Simply drawing 
attention to the people responsible for libxo's inclusion
in FreeBSD that they need to fix it.

> > Do you really believe that the Nd entries for these manpages are
> > correct?
> >
> 
> I'm not an expert on the mdoc format, so I couldn't tell you.
> If you can think of some patches to fix things, in the man pages,
> would you be able to submit the patches to Phil, and have them incorporated
> into the software to make it better?

There isn't a public mailing list or other mechanism to 
submit a patch.  One needs to sign up for an account.
I have way too many accounts on way too many systems
to sign up for a new account to send in a single patch.

> libxo is maintained at https://github.com/Juniper/libxo .
> 
> I don't know if you are willing/able to submit patches to the libxo project
> on Github,
> to help fix things.  That would be great if you could do that and help out.

It seems that libxo developers have no interest in FreeBSD documentation.

https://github.com/Juniper/libxo/issues/13

Those that imported/maintain libxo within FreeBSD should fix the
documentation.

-- 
Steve


More information about the svn-src-head mailing list