Re: git repo port issues?

On Thu, Jan 4, 2024, 12:14 PM Jamie Landeg-Jones <jamie@catflap.org> wrote:

> Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote:
>
> >
> > Or create database (key-value store would be sufficient) storing commit
> > order (like r* of svn) and commit hash.
> > I'm still not certain whether commit order or commit hash should be the
> > "key". Possibly store hash as the key fisrt and store assigned MONOTONIC
> > order as value, then, add the just-stored order as key and hash as
> > value in another database would be neeed. If the database can contain 2
> > value for 1 key, it would be suitable for you to store the assigned
> > time in UTC as "when it is committed to FreeBSD master repo".
>
> I do miss the incrementing "r" value - it's a nice immediate way to
> tell which update is more recent. Actually, to me, that is more important
> than the date - I've attempted to base my changes on the date due to the
> absense of such a useful field.
>

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...

Also be advised that the pre FreeBSD 8 or so tree still has some surprising
artifacts in it.

Warner

Actually, I think I may implement such a thing on my local cgit repo.
>
> https://cgit.dyslexicfish.net/ports/latest/tree/
> https://cgit.dyslexicfish.net/src/current/tree/
>
> Cheers, Jamie
>
>