Re: git repo port issues?

Warner Losh <imp@bsdimp.com> wrote:

> See sys/conf/newvers.sh for the 'n' value we use in uname strings.  It's a
> linear count of commits on the first-parent branch back to the start of the
> repo.
>
> Also, the dates usualy are first order correct and i use them for the stats
> i run. Though I've also just dropped tags on the first commit of each year
> too...

Ahhh brilliant, thanks! I didn't know about that. That looks like just what
I'm after.

Is it safe to assume that all commits in a cloned and then fetched/pulled
repo will have the commits in the same order as the parent?

Also, are "null commits", where there is a commit but no actual files commited
(not sure what those are for!) counted too? 

(example: https://cgit.dyslexicfish.net/src/current/commit/?id=cb4ff25c8a40e6811f48f6ad03a0bf882404e9ac )

I'll never understand the nuances of operating day to day with git like you
guys, so I'm grateful for the help and patience you have shown, especially
when I come out with an idea that is basically dumb.

Cheers, Jamie