From owner-freebsd-current@FreeBSD.ORG Sun Mar 1 16:46:50 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A5056666; Sun, 1 Mar 2015 16:46:50 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 834CF6BE; Sun, 1 Mar 2015 16:46:50 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id t21GkiKm069675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 1 Mar 2015 08:46:44 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id t21Gkil4069674; Sun, 1 Mar 2015 08:46:44 -0800 (PST) (envelope-from sgk) Date: Sun, 1 Mar 2015 08:46:44 -0800 From: Steve Kargl To: Allan Jude Subject: Re: Massive libxo-zation that breaks everything Message-ID: <20150301164644.GA69625@troutmask.apl.washington.edu> References: <54F31510.7050607@hot.ee> <54F33D99.2060102@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54F33D99.2060102@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2015 16:46:50 -0000 On Sun, Mar 01, 2015 at 11:26:01AM -0500, Allan Jude wrote: > On 2015-03-01 08:33, Sulev-Madis Silber (ketas) wrote: > > Is there a specific bug you are running in to? So far the only bugs I've > seen with the xo-ification have been ones where the JSON output was not > always well formed. > Given the poor quality of the manpages, it does lead one to wonder about the quality of the library code. -- Steve