From owner-freebsd-current@freebsd.org Sat Aug 29 16:04:47 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 530413B4CC1 for ; Sat, 29 Aug 2020 16:04:47 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bf1WM1ZJYz3Sfq; Sat, 29 Aug 2020 16:04:47 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id C263980C2; Sat, 29 Aug 2020 16:04:46 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Sat, 29 Aug 2020 16:04:44 +0000 From: Glen Barber To: Michael Butler Cc: freebsd-current Subject: Re: documentation on release build process change (svn -> git)? Message-ID: <20200829160444.GC19857@FreeBSD.org> References: <20200828174307.GC61041@FreeBSD.org> <20200828174424.GD61041@FreeBSD.org> <20200829151406.GA19857@FreeBSD.org> <95d7aef5-69d4-0215-43ca-0663bc370667@protected-networks.net> <20200829155123.GB19857@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4ZLFUWh1odzi/v6L" Content-Disposition: inline In-Reply-To: <20200829155123.GB19857@FreeBSD.org> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1598717087; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ZCfuFGmH6gBGDPblGue+J8J4aZvEYZt0nbwhmbWi7h0=; b=FvsaW2mwTsZShVHJjUaTl5ilZNyrS3cMfMVZkoQxSJwi4ZTcqlX1oT8hZDGOXoICRA8B6x 4gNgNNZ8ZzwAVoJtwX3MTwhQyHhvsp1PsJ++o56xNaQkof96H2pVFedLNrbUlW/18GgPoA TohxQ/81522NH9G4uq45jMjwBQI7K34mCBcLfqLujku8f3DbS9PQRP2wgrXG/Ud8NebeGL 1zG1tIHIURW9rd2H7oS5KuInA5hdkZjNP2hwDys82FaOkF07f14l0/LpdVfKbbJ9D5E2Ps C3Mal9kqWWuDuswmZcIqbgnuFpeHMYWx4vFBGheC++aELC3bcpjNjcFUOyI27A== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1598717087; a=rsa-sha256; cv=none; b=DEh2uoTt5C72uykZT0dGXhuEfNlPHQcM/z1nRIt1nc/a8z4c1wLUuZGraD4NLaKGmif5m6 IMaxkc5y0MBt7vqysoxEp0P3AQeL34+mpSexRM1qVpHARUYuvANxAg+1iHWKFwmDg+A1ns KbdZOczowy+WM8D3fXygHxHub68/MCNlX2L9mmJs3VIleqdTWaNS5MMeSzoIBJrU3UDi5m Th6WAU8Fn9ZhUwwp1v24B4jAcbku0TcDRi2OhRR9NX/JsRt5wVGKTmYKfjm0Utz5ktUs29 MBHzMQ4jledGYJzHwICoONjZM9hkfNqIkjrzmnqtP57khb5JF6tPYjRDuJ020Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Sat, 29 Aug 2020 16:04:47 -0000 --4ZLFUWh1odzi/v6L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 29, 2020 at 03:51:23PM +0000, Glen Barber wrote: > On Sat, Aug 29, 2020 at 11:34:15AM -0400, Michael Butler wrote: > > On 8/29/20 11:14 AM, Glen Barber wrote: > > > NOPORTS=3Dyes is the problem, and I forgot to address it before mergi= ng > > > the project branch back. Please try with r364956. > >=20 > > Trying now but, in the interim, I noted .. > >=20 > > With SVN, I could re-use a previously existing build directory and it > > would simply apply the relevant diffs to bring the tree up to date. > >=20 > > In the move to GIT, now it seems I have to pull the whole tree down or > > it complains .. > >=20 > > imb@vm01:/usr/src/release> sudo ./release.sh -c release-i386.conf > > fatal: destination path '/usr/local/release-builds/i386/usr/src' already > > exists and is not an empty directory. > >=20 > > I'm not that familiar with GIT but .. Is there an incremental update > > option I can use? If so, should this be the default? As is, it seems > > like a colossal waste of bandwidth and unwanted load on the parent GIT = repo, > >=20 >=20 > I added a way to update an existing tree in r364959. I have only done > very trivial testing on this change, however, so please let me know if > it does not work as expected. >=20 r364960 further refines how this works; that would be a better revision to use to test. Glen --4ZLFUWh1odzi/v6L Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl9KfJwACgkQAxRYpUeP 4pNQNA//epwFGJO52qplkfpfGeblcYkfpw8DYlCb/lsGggOXSwLfrWh/j6N8wC6C 5NfvQhlc5W+z+x/O46B/RLHqJNmiF3nVxWvOEGeSjimD7fuTdpeHhng9A6wefAhp ivC1TX/JtWu1tb7jXGnDQ+cOK2sxNETVSE3SIKnkKcNxQOCJvsKX34MpnZDPJws6 cQ+e5frEQksKdalU10EMG5NTCjvTGGJO7ubYDXwbrPQJa69D0jatByMb+qD9Az9I OmPxyWNLONxjefrqC+a23XbSb+VOqLK1ueoBVoMjTKSk068ZRbiIUyOaSYBKt+J+ 0OaiCwn2r/oVooDsuFgGpT8lytLRgNOgZlcjj1govFJcMh7uqTxTOr8uijcRmfPM w0EFhR1BiIFg0FbkbqwNpHig9WpVgDfJ8uvGga9ov0Rwk5rvIA2oBN75xJXb2EQD p31ks7QxWA5qW0QX2/IUS4cLM6ONBYmVjCWRn/GwghKJaVXmuw8okGwmYMO/cv/E U1xpRtEEE259/lHmdZ+6V+znHiE3E9YOnGig2VhWkM6xOskdREFxGZ8f8EWpn2Iz lnx1icwc7AlZaa0crsfgv0/OGcNPGrGyfkAoAhta09AGm4SDW0hDMW+Xa/nb07iG Jg+S9pGnaU9XFQoVPQQiIVv4NPLGYIR+t4y3esM2yTV25YgTa0A= =Lexs -----END PGP SIGNATURE----- --4ZLFUWh1odzi/v6L--