Git, shallow clone hashes, commit counts and system/security updates

From: Graham Perrin <grahamperrin_at_gmail.com>
Date: Tue, 2 Mar 2021 06:33:05 +0000
On 02/03/2021 05:42, Kevin Oberman wrote:

Re: Panic after updating from source
> On Mon, Mar 1, 2021 at 6:31 PM Michael Sierchio <kudzu_at_tenebras.com> wrote:
>
>> …
> You need to be aware that the shallow clone hash will not include the
> commit count which will be used in future security updates to make it easy
> to check whether your system needs to be updated or not. A full clone does
> require more space, but I was surprised at how little extra space it
> requires. Warner  is updating his git mini-guide to point out this issue.
> If you run STABLE, it's a really significant concern. You can convert the
> shallow clone to a full one with "git fetch --unshallow". This will take
> some time to run.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman_at_gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> _______________________________________________
> freebsd-questions_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions

Drawing the above (with a change of subject line) to the attention of 
the freebsd-current list.

Thank you, Kevin and Warner.
Received on Tue Mar 02 2021 - 05:33:09 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:27 UTC