On Sun, 26 Jun 2022 23:37:42 +0300, Damyan Ivanov wrote: > $ stat .git/FETCH_HEAD > File: .git/FETCH_HEAD > Size: 2055 Blocks: 8 IO Block: 4096 regular file > Device: 2eh/46d Inode: 1037725 Links: 1 > Access: (0644/-rw-r--r--) Uid: ( 1000/ dam) Gid: ( 1000/ dam) > Access: 2016-11-09 20:22:16.102958000 +0200 > Modify: 2019-09-15 14:56:51.696968093 +0300 > Change: 2021-11-04 15:42:45.072112725 +0200 > Birth: 2021-11-04 15:42:45.072112725 +0200 % stat .git/FETCH_HEAD File: .git/FETCH_HEAD Size: 2481 Blocks: 8 IO Block: 4096 regular file Device: fe03h/65027d Inode: 7291655 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ gregoa) Gid: ( 1000/ gregoa) Access: 2021-01-31 08:30:28.390935982 +0100 Modify: 2021-01-30 20:11:20.295060888 +0100 Change: 2021-01-30 20:11:20.295060888 +0100 Birth: 2021-01-30 00:06:18.427682314 +0100 > compare-lastactivity looks at the ctime (i-node/metadata change time). > Perhaps it should look at the mtime (data change time)? That's an interesting idea. Maybe worth trying? :) > The filesystem where the repositories reside is mounted with the > 'relatime' option and perhaps this has some side effects not > considered by compare-lastactivity? I don't think so, as I'm also using relatime. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `-
Attachment:
signature.asc
Description: Digital Signature