From owner-freebsd-arch@FreeBSD.ORG Sun Jan 4 05:28:48 2015 Return-Path: Delivered-To: freebsd-arch@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 CE32F1DF; Sun, 4 Jan 2015 05:28:48 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id B82DC645EC; Sun, 4 Jan 2015 05:28:48 +0000 (UTC) Received: from AlfredMacbookAir.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 24961341F875; Sat, 3 Jan 2015 21:28:48 -0800 (PST) Message-ID: <54A8CFBB.5090609@freebsd.org> Date: Sat, 03 Jan 2015 21:29:31 -0800 From: Alfred Perlstein Organization: FreeBSD User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Phil Shafer Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML References: <201501040510.t045AU6i079716@idle.juniper.net> In-Reply-To: <201501040510.t045AU6i079716@idle.juniper.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "adrian@FreeBSD.org" , Marcel Moolenaar , "Simon J. Gerraty" , Poul-Henning Kamp , freebsd-arch , Konstantin Belousov , Garrett Cooper X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2015 05:28:48 -0000 On 1/3/15 9:10 PM, Phil Shafer wrote: > Alfred Perlstein writes: >> Would like to expedite process here, I'm going to check in a few interim fixes so that p >> eople can continue hackathon on libxo over the holiday break. When you're back please f >> eel free to revert/modify my changes. > > I'm happy to import fixes in any form (and am currently addressing > the D1378 and D1379), but the simplest way for me would be a fork > on the github sources. Not sure how hard that makes things on your > end, esp. re: importing of next libxo release. It's with, with git I can find a way. What I should have done, and will likely do is use either "git subtree" or "git submodule" in my 'libxo_master' branch to track a forked (github forked, not Open/NetBSD forked). This will allow us to track juniper's libxo. Shouldn't be a problem. > > Also: sorry for the slow responses. I was on vacation for most of > December, with multiple overlapping sets of relatives in town. Life > is returning to normal now. No worries, welcome to 2015! -Alfred