Hi,
When I want to check if a particular commit is expected to be present in a
particular kernel, I usually check the dates.
$ what bsd.mp
OpenBSD 7.1-current (GENERIC.MP) #481: Thu Apr 21 21:11:42 MDT 2022
$ cvs log dev/usb/if_ral.c
[...]
----------------------------
revision 1.149
date: 2022/04/21 21:03:03; author: stsp; state: Exp; lines: +2 -3;
commitid: 71y4MGxVttLEpbpK;
Use memset() to initialize struct ieee80211_rxinfo properly.
[...]
The problem is cvs (or got) is using date using UTC whereas the kernel is using
localized date (here MDT, but could be CEST in my case too if I build the
kernel
myself).
Whereas I know that the build time isn't necessary a perfect indication of the
presence of a particular commit (specifically if the time interval is small),
it
might be more simple to compare date if both are in the same timezone.
Currently, I am using such command to convert MDT to UTC:
$ TZ=Canada/Mountain date -j -z UTC 202204212111
Fri Apr 22 03:11:00 UTC 2022
but the input format (202204212111 for 'Apr 21 21:11:42 MDT 2022') isn't
particulary straightfor to write.
Does such diff to force UTC timezone in kernel buildate would be acceptable ?
Please note that both cvs(1) and got(1) are ignoring TZ environment variable,
so
I can't get them to show directly MDT dates.
Thanks.
--
Sebastien Marie
diff 62198fa5a9d005ca1c651b3df2c33ce50d333b27 /home/semarie/repos/openbsd/src
blob - ab97ce4c59639a6b357120b9a953c3584211aea2
file + sys/conf/newvers.sh
--- sys/conf/newvers.sh
+++ sys/conf/newvers.sh
@@ -40,7 +40,7 @@ then
fi
touch version
-v=`cat version` u=`logname` d=${PWD%/obj} h=`hostname` t=`date`
+v=`cat version` u=`logname` d=${PWD%/obj} h=`hostname` t=`date -z UTC`
id=`basename "${d}"`
# additional things which need version number upgrades:
