Date: Fri, 26 Feb 2021 13:54:58 -0500 From: Ed Maste <emaste@freebsd.org> To: Helge Oldach <freebsd@oldach.net> Cc: freebsd-stable stable <freebsd-stable@freebsd.org>, Warner Losh <imp@bsdimp.com> Subject: Re: How do I know if my 13-stable has security patches? Message-ID: <CAPyFy2B8u=ZECk8W9Ch7ovsC9DRN9JXwWy2=2U1jJEOsMK3Z_g@mail.gmail.com> In-Reply-To: <202102261710.11QHAVLY062611@nuc.oldach.net> References: <CAPyFy2BBT1kffwRwN5D1km0ozyiLFMPP7sGM_J0b6auLhzPY9A@mail.gmail.com> <202102261710.11QHAVLY062611@nuc.oldach.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 26 Feb 2021 at 12:10, Helge Oldach <freebsd@oldach.net> wrote: > > A shallow tree is about 1.6G. If you want to patch source (say, from > a SA or EN) you certainly also need space for an object tree which is > about 4.5G. The total is >6G. > > I'd say relative to the total required to build, the 1.1G "savings" from > using a shallow versus a full tree (which is about 2.7G) isn't really > worth the effort. Plus, you get the a few benefits like full commit > history including comments. Indeed, this is a good point. We can update docs to state: At present a full clone is required to include the commit count in uname. An existing shallow clone can be converted into a full clone by running % git fetch --unshallow
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2B8u=ZECk8W9Ch7ovsC9DRN9JXwWy2=2U1jJEOsMK3Z_g>