documentation on release build process change (svn -> git)?

[Glen Barber]

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=yes is the problem, and I forgot to address it before merging
> > > the project branch back.  Please try with r364956.
> > 
> > Trying now but, in the interim, I noted ..
> > 
> > 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.
> > 
> > In the move to GIT, now it seems I have to pull the whole tree down or
> > it complains ..
> > 
> > imb at 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.
> > 
> > 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,
> > 
> 
> 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.
> 

r364960 further refines how this works; that would be a better revision
to use to test.

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20200829/d4f4ffed/attachment.sig>