Date: Sat, 29 Aug 2020 16:04:44 +0000 From: Glen Barber <gjb@freebsd.org> To: Michael Butler <imb@protected-networks.net> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: documentation on release build process change (svn -> git)? Message-ID: <20200829160444.GC19857@FreeBSD.org> In-Reply-To: <20200829155123.GB19857@FreeBSD.org> References: <cc3e3579-6ff8-89d4-f713-7672836143a4@protected-networks.net> <20200828174307.GC61041@FreeBSD.org> <20200828174424.GD61041@FreeBSD.org> <aa7989d6-eed5-9575-09bb-536680629e61@protected-networks.net> <20200829151406.GA19857@FreeBSD.org> <95d7aef5-69d4-0215-43ca-0663bc370667@protected-networks.net> <20200829155123.GB19857@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200829160444.GC19857>