From owner-freebsd-current@freebsd.org Sat Aug 29 15:51:25 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 E43D73B44C8 for ; Sat, 29 Aug 2020 15:51:25 +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 4Bf1Cx5lzZz4fxW; Sat, 29 Aug 2020 15:51:25 +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 668DE7C88; Sat, 29 Aug 2020 15:51:25 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Sat, 29 Aug 2020 15:51:23 +0000 From: Glen Barber To: Michael Butler Cc: freebsd-current Subject: Re: documentation on release build process change (svn -> git)? Message-ID: <20200829155123.GB19857@FreeBSD.org> References: <20200828174307.GC61041@FreeBSD.org> <20200828174424.GD61041@FreeBSD.org> <20200829151406.GA19857@FreeBSD.org> <95d7aef5-69d4-0215-43ca-0663bc370667@protected-networks.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="A6N2fC+uXW/VQSAv" Content-Disposition: inline In-Reply-To: <95d7aef5-69d4-0215-43ca-0663bc370667@protected-networks.net> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1598716285; 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=3TWge8QSmCNRNNvNYcotjYHmJE6MfLQ7ZmtB05s0KUE=; b=S0/5VlLzNKO9/a+aVXPdsuh61YTN8L0x9un5kQ0dlIQxuAfqQtqmSwNErchv9q/EtEPQwT L37zjylBG/5RjBpQRf7KqPPT2hKnu9Ob9a7JsfGse7cCx23pTEJjKN+9iYpxGIeRqDuNvm xBqw+H7WYX2ZMteygAJzTC4iYcMQX5wX/UPfRtCAEBl2aUiLIHBOChlUoPfn+eWGC9btuA qSV8o6DaUHQnyUeLBhKavfbAiNmkdgXaOZQHIUqGUKN9A/kIK+su3EOIR8Eb6YPBEXFfos 8LJLjgbsGebHmP64reG5Tk209Yy+UkgqXr/p2ZcHdpwzdWrlVSt/YBjcjYWF/A== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1598716285; a=rsa-sha256; cv=none; b=WbBmfV1XI3EzyOTJ0jVsOc+RaGdbx2BaZGKVQmpEMw3lYVbWgSuR+6ERpqFi91jjn2vQKs ZiOz3uF6MVsPSG9Wt0AFPWJe8alTOXcsxhJjo9pr2VYldPsJE0hJX8wacs9KClLr1lipks VYPsCyvmNkaO0Yb+JwXmGsSzaq2w2Q2PUUGJJoiDLZ/q616snPsbttNS2BHTzDYC9JfVZN ddc6ml/0TStwV8uLJFfv0nXuZ+RGRYgauzFHHt3gedjk5FHRvbuM3hlq5iFjERU8FVuP0o 2pDBSwmvz0IGw3p7VcSuO5XxjmW8rWV2rAh7hP3sAwF5YBJX2R4IvO0ZJF016A== 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 15:51:26 -0000 --A6N2fC+uXW/VQSAv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 merging > > 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 re= po, >=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. Glen --A6N2fC+uXW/VQSAv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl9KeXsACgkQAxRYpUeP 4pNDtw/+N4TUZK/lKk7D747qxZXGpcKhztY0h4xjCtZjNaUaFbZ+LfdHvZSF0Y7t IRHWNJuMaot8trsXIGInC0dTiyLPIKXM4fbGapISOmrj0SyJ6Cne/G+LKV3tiyYB ewV7FxdXN+ATaOyVi6+UqGef2PWSuogh4aLOlfH2f4yEIY0hY/S7Z+vAiVRzgAEr jFuPw54gnrs+GFs9R1iB25IowFcugZ+LYRPpIySFg06XStNFOoPkTHNFiUYnds4b 6o78oehqH1X2dQpsLfb1uH1ounWYNSCzJZnM62DHgtgC/G2XAYwrvXsR1TO1f1ja PGlSbZWlBCEEmbk75sOiffplv48YXKhUASX3Kz+6BkeJhYkhV9Bs+Vid5HL29+6j XhNpGoxK8EwgKHRE6ubCdUzkRT0GLYGukBqt3O/7crSpMQYIl7aNoZgVikJw5cF6 380spTUbFKilpSelvPCyQXhv0F4bRkek3cOqapuXND/+0Hd//oxjNwGMkrf0abhZ 84hCAyzpoZV6cywYhdQ8rXu3FcJZp6ltvETJA5fuCXZFzJAHaOqgdFq2hVKkaQvS s1QvzVgWYkfiAyfti9dJ7bY/sPzbRdRPTiVQ/HSUsmh6Qcj2BIkijdCMrYtkEa53 ZlaiqK+L0wEG8Lqo0t+VhYw8hUqupOqzU7QLucHvILWuG28mzhI= =Qzuy -----END PGP SIGNATURE----- --A6N2fC+uXW/VQSAv--