On Fri, 2015-06-12 at 19:49 -0700, Steve Kargl wrote: > On Fri, Jun 12, 2015 at 08:43:09PM -0400, Alexander Kabaev wrote: > > On Wed, 10 Jun 2015 01:27:39 +0000 (UTC) > > Marcel Moolenaar <mar...@freebsd.org> wrote: > > > > > Author: marcel > > > Date: Wed Jun 10 01:27:38 2015 > > > New Revision: 284198 > > > URL: https://svnweb.freebsd.org/changeset/base/284198 > > > > > > Log: > > > Convert ls(1) to use libxo(3). > > > > > > Obtained from: Phil Shafer <p...@juniper.net> > > > Sponsored by: Juniper Networks, Inc. > > > > > <SKIP> > > > > This broke all code that pipes output of the ls command to pipeline, > > such as 'ls | wc -l'. ls never exits and never output anything. Is > > there any purpose to libxo other than breaking stuff, which it achieves > > so splendidly? > > > > -1 for libxo, which also makes code almost unreadable. >
s/unreadable/unmaintainable/ If you would have told me a year ago that you had a simple scheme that could make 30 years of experience maintaining code for unix-like systems completely worthless I would have been skeptical, but it seems we're well on our way. -- Ian _______________________________________________ svn-src-head@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
