From owner-freebsd-current@FreeBSD.ORG  Wed Apr  2 22:59:00 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7CFE46D5;
 Wed,  2 Apr 2014 22:59:00 +0000 (UTC)
Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40])
 by mx1.freebsd.org (Postfix) with ESMTP id 5EB2C7F0;
 Wed,  2 Apr 2014 22:58:59 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
 id A5E885607C; Wed,  2 Apr 2014 17:58:58 -0500 (CDT)
Date: Wed, 2 Apr 2014 17:58:58 -0500
From: Mark Linimon <linimon@lonesome.com>
To: sbruno@freebsd.org
Subject: Re: login.conf --> UTF-8
Message-ID: <20140402225858.GA4211@lonesome.com>
References: <201404022206.s32M6DD4090396@hergotha.csail.mit.edu>
 <1396479395.2280.21.camel@powernoodle.corp.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1396479395.2280.21.camel@powernoodle.corp.yahoo.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Garrett Wollman <wollman@hergotha.csail.mit.edu>, current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 22:59:00 -0000

On Wed, Apr 02, 2014 at 03:56:35PM -0700, Sean Bruno wrote:
> I have been informed by folks that this change I suggest would help in
> the case of ports having to declare UTF-8 support explicitly or
> something.

Clearly ports that need to do this are broken -- but this very much an
edge-case of brokenness.  There's so much other lower-hanging fruit than
to fix the individual offenders.

mcl