From owner-freebsd-stable@FreeBSD.ORG Tue Apr 23 00:06:05 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2D52CB56; Tue, 23 Apr 2013 00:06:05 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 06C3F1EB6; Tue, 23 Apr 2013 00:06:05 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 2E7AD23F804; Mon, 22 Apr 2013 20:06:04 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us 2E7AD23F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 22 Apr 2013 20:06:02 -0400 From: Glen Barber To: Jeremy Chadwick Subject: Re: svn revision stable/9 Message-ID: <20130423000602.GB1606@glenbarber.us> References: <000901ce3fb3$31732a50$94597ef0$@gmail.com> <20130423000004.GA17734@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ADZbWkCsHQ7r3kzd" Content-Disposition: inline In-Reply-To: <20130423000004.GA17734@icarus.home.lan> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Scott Reber , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 00:06:05 -0000 --ADZbWkCsHQ7r3kzd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 22, 2013 at 05:00:04PM -0700, Jeremy Chadwick wrote: > I'm not sure where this comes from during buildkernel, however. "svn > info" is the way I know of to get that value, but I don't know where in > the build framework it obtains this number. >=20 svnversion is called in sys/conf/newvers.sh to get the revision. > The reason I mention that: possibly the build framework uses the "svn" > command to get the information, and since "svnup" is not "svn", it can't > get it, thus there's nothing to print. >=20 svnversion is the specific binary that is required, but svnup does not pull in metadata. Glen --ADZbWkCsHQ7r3kzd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRddBqAAoJEFJPDDeguUajEUAIALPtR7OkkVk21phyMgQeI219 3OBAeMWkLpf94H3gZ/wWQ5OD771BtAjfyDuNPOnT1H3DvcM3z2sRyyxAE1FP/Bhz Loa4Yz7iYYUIMcL+Alg5pogNelyLPIQAZWo+IMkmpdnXK7lTcYrzf+P2yC25YxSX 8pKRGl4gG0svWZdcpQa5TjsQnSzSHXSybOlOVv6WocM2yu0jBkvVDqi4aNILpixn s3/DPtj4Jrd6c1L+Sdfnc27l9F1U8vwe+LbC6BsdWcKPbqLMIpCMOpbFwqqcqlrs IgKuYGlnMjtEij2jFo3feNBBnqN6EEKkRXLJ6L9sLFlY0TDAr0UKpuVb5s5NVLE= =4osI -----END PGP SIGNATURE----- --ADZbWkCsHQ7r3kzd--