Re: phantom version numbers?
- In reply to: Steve Kargl : "Re: phantom version numbers?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 28 Feb 2025 18:49:04 UTC
On Feb 28, 2025, at 10:34, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > On Thu, Feb 27, 2025 at 09:02:48PM -0800, Mark Millard wrote: >> Steve Kargl <sgk_at_troutmask.apl.washington.edu> wrote on >> Date: Thu, 27 Feb 2025 18:52:17 UTC : >> >>> IMHO, the solution is clearly wrong. INDEX-15 is only >>> valid for short period of time. Hmmm, it seems that >>> the Porter's Handbook >>> >>> https://docs.freebsd.org/en/books/porters-handbook/book/#versions >>> >>> shows that __FreeBSD_version was changed to 1500030 on 2025-01-02. >>> Newer numbers are not documented. My kernel is at 1500031 with >>> a timestamp of >>> >>> kern.version: FreeBSD 15.0-CURRENT #0 main-n275407-e736f6df1ec1:\ >>> Wed Feb 12 15:22:12 PST 2025 >>> >>> and INDEX-15 is from a system with 1500033. 'git blame' shows >>> >>> 05dfaadde4ae0 (Jean-Sébastien Pédron 2024-12-22 19:10:23 +0100 76)\ >>> #define __FreeBSD_version 1500033 >>> >>> So, the timestamps don't make sense. >> >> You are using a tools in ways that shows authorship dates instead of >> commit dates: > > That is certainly possible. It is unfortunate the FreeBSD switch > from svn to git, but that a horse of a different color. > >> author Jean-Sébastien Pédron <dumbbell@FreeBSD.org> 2024-12-22 18:10:23 +0000 >> committer Jean-Sébastien Pédron <dumbbell@FreeBSD.org> 2025-02-19 20:39:46 +0000 > > % git log sys/param.h > > commit 05dfaadde4ae0f5d823836d5d849e3ba5ebdbf17 > Author: Jean-Sébastien Pédron <dumbbell@FreeBSD.org> > Date: Sun Dec 22 19:10:23 2024 +0100 > > linuxkpi: Add `shrinker_alloc()` and `shrinker_free()` > > They are used by the DRM drivers in Linux 6.7. > > Bump `FreeBSD_version` because external drivers that use `struct > shrinker` will have to be recompiled. > > Reviewed by: bz > Sponsored by: The FreeBSD Foundation > Differential Revision: https://reviews.freebsd.org/D48747 > > So, the date here is completely useless and there is no indication > of when the commit actually occurred. As 'git log' should be an > easy way to see the history of a file, why is the date the change > was recorded in HEAD not displayed? # git log --pretty=fuller Shows the likes of: commit <hash> Author: <author> AuthorDate: <author-date> Commit: <committer> CommitDate: <committer-date> <title-line> <full-commit-message> For just the commit date/time sort of information, there is: # git log --pretty=format:%cd # Example; the committer dates formats are: %cd committer date (format respects --date= option) %cD committer date, RFC2822 style %cr committer date, relative %ct committer date, UNIX timestamp %ci committer date, ISO 8601-like format %cI committer date, strict ISO 8601 format %cs committer date, short format (YYYY-MM-DD) %ch committer date, human style (like the --date=human option of git-rev-list(1)) === Mark Millard marklmi at yahoo.com