Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Jun 2015 04:09:29 -0700
From:      Garrett Cooper <yaneurabeya@gmail.com>
To:        Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        Craig Rodrigues <rodrigc@FreeBSD.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>
Subject:   Re: svn commit: r284198 - head/bin/ls
Message-ID:  <BD75A249-0A8A-48F4-A92B-F102508903AE@gmail.com>
In-Reply-To: <20150614060935.GA3889@troutmask.apl.washington.edu>
References:  <20150613024916.GA98218@troutmask.apl.washington.edu> <1434208622.1415.57.camel@freebsd.org> <C88CB169-12FE-4692-92AA-5C7D41BB61DF@FreeBSD.org> <557C661F.8080104@freebsd.org> <860017ED-D754-450C-865D-2D81A30C2212@xcllnt.net> <CAG=rPVd93Q18aYnSGSf_QH4C08RCq5wsdKQSNYTgWQ2huTbUHQ@mail.gmail.com> <20150614002640.GA2746@troutmask.apl.washington.edu> <CAG=rPVfrM9SnqRU-g=L6Y39GM2yEd%2Bt6=UFhggauu0s3HJvpYw@mail.gmail.com> <20150614012924.GA2965@troutmask.apl.washington.edu> <CAG=rPVdYQe3robA6WtMxubRfzjYU3bHx==Cgx70rJxd6T=66%2Bg@mail.gmail.com> <20150614060935.GA3889@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_D0207CB8-6EF1-4A13-8660-9E54A9B19E16
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Jun 13, 2015, at 23:09, Steve Kargl =
<sgk@troutmask.apl.washington.edu> wrote:

> 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@troutmask.apl.washington.edu> wrote:
>>=20
>>>>=20
>>>> Are you talking about this comment you made?
>>>>=20
>>> =
https://lists.freebsd.org/pipermail/freebsd-current/2015-March/054899.html=

>>>>=20
>>>> I can't make heads or tails of what you wrote, other than you =
seemed very
>>>> angry.
>>>>=20
>>>=20
>>> I wasn't very angry.
>>=20
>> 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.
>>=20
>=20
> 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.

I see the benefit in libxo, but I see the argument in it being =
unnecessary bloat as well.

>>> Do you really believe that the Nd entries for these manpages are
>>> correct?
>>>=20
>>=20
>> 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?
>=20
> 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.

Github is rather straightforward, but yes.. the workflow=92s a bit =
different:
1. Fork project.
2. Create a branch for a =93topic=94 (i.e. fix/enhance X).
3. Open a pull request (which will open an issue).

>> libxo is maintained at https://github.com/Juniper/libxo .
>>=20
>> 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.
>=20
> It seems that libxo developers have no interest in FreeBSD =
documentation.

Not entirely true. They=92re willing to work on the versioning problem I =
noted in the above issue.

> https://github.com/Juniper/libxo/issues/13
>=20
> Those that imported/maintain libxo within FreeBSD should fix the
> documentation.

The problem was with the manpage to github link referencing -- which can =
change. FWIW I=92m happy they have documentation, unlike our current =
defacto toolchain in FreeBSD (man clang makes me sad=85 I keep gcc =
installed just so I can refer to something halfway decent):

             -O0     Means "no optimization": this level compiles the =
fastest
                     and generates the most debuggable code.

             -O1     Somewhere between -O0 and -O2.

             -O2     Moderate level of optimization which enables most
                     optimizations.

Really clang? I didn=92t realize that 1 was between 0 and 2...

Thanks.

--Apple-Mail=_D0207CB8-6EF1-4A13-8660-9E54A9B19E16
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJVfWDtAAoJEMZr5QU6S73efR0H/A0Dl08yqBkoDVbgdmlrDDwM
MDmgP4MXaPmLFJk1KJtED0GodWyPQ0CyLj2lcMHnNIzz+v1kfofNI8oqWFf7yC8W
/hohx9HGwCnM7bNiKzPmp+jWjfNyuUHZybn+53SBzIHzFgslWxy8UWFRZN86z30/
7GOceCwWPkKKPUkOmHNS4dWxlmj7WuAp46YHYoo/H2uZKfFJmrEVp+zL/ts95X81
YK8s6MXGUNLGwiTDQFonj9eHL/v2IbvUWvzCoreX0UTkR/77Q1+rSlgKRUcmIMwI
QpUIwLZwzCkyOVSLNk4G4TjI/XQMI6JI2lFvRqTOzNjG2/Mi7Fv+qydDnY27fjc=
=T7OB
-----END PGP SIGNATURE-----

--Apple-Mail=_D0207CB8-6EF1-4A13-8660-9E54A9B19E16--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BD75A249-0A8A-48F4-A92B-F102508903AE>