Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Aug 2018 14:32:54 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Ian Lepore <ian@freebsd.org>
Cc:        "Rodney W. Grimes" <rgrimes@freebsd.org>, Kyle Evans <kevans@freebsd.org>,  Adam Weinberger <adamw@adamw.org>, svn-src-stable@freebsd.org, svn-src-all@freebsd.org,  src-committers <src-committers@freebsd.org>, Ed Maste <emaste@freebsd.org>,  svn-src-stable-11@freebsd.org
Subject:   Re: svn commit: r337826 - stable/11/bin/ls
Message-ID:  <CANCZdfq64Ln6BPzz3UFubxOfHQfYTaHuLpyx_tXYY4b2MjJR1A@mail.gmail.com>
In-Reply-To: <1534364937.1466.11.camel@freebsd.org>
References:  <201808152026.w7FKQGBN049627@pdx.rh.CN85.dnsmgr.net> <1534364937.1466.11.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 15, 2018 at 2:28 PM, Ian Lepore <ian@freebsd.org> wrote:

> On Wed, 2018-08-15 at 13:26 -0700, Rodney W. Grimes wrote:
> > >
> > > Will backing out the MFC and leaving this a 12.0 feature end this?
> > =(
> >
> > Sadly no, as the person responded with that reaction when
> > they installed 12.0-ALPHA :-(.
>
> So one whiner can demand of the project that any new feature be removed
> before a new release is made?
>

This is a good change. I don't see why people are so fussed about it... For
people fighting colored environments a simple unsetenv COLORTERM seems to
solve this problem no only on FreeBSD but for any other system they have
access to...

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfq64Ln6BPzz3UFubxOfHQfYTaHuLpyx_tXYY4b2MjJR1A>