Re: uname -v does not report an n-number

On Wed, Aug 20, 2025 at 10:42:26PM +0200, Dag-Erling Smørgrav wrote:
> bob prohaska <fbsd@www.zefox.net> writes:
> > [...] IIRC it's possible to "set a depth", could it be set to some
> > small number, like 1, 2 or maybe 3, so I get the N-number without all
> > the baggage?
> 
> What you call “the N-number” is literally the depth of your repository.
> If you clone with --depth=5 then it will show up as 5.  You can test it
> yourself with `git rev-list --first-parent --count HEAD`.

I was thinking it could be computed from the master repository, since I'm
making no local changes to /usr/src. 

> 
> A full clone is less than 3 GB, though, and if you're on ZFS, you can
> save quite a bit by making /usr/src and /usr/obj separate datasets and
> turning on compression.
> 
Right now /usr/src is a little over 3 GB. The machine could still function
if /usr/src grew to 6 or 7 GB. Right now a Pi4 running -current is only
using a little under 4 GB. That could be lived with. It looks like 
git pull --unshallow 
will bring in what's missing, will it give me a sensible n-number?

Thanks very much for writing!

bob prohaska
.