Julia Evanspoll: when you see this message in `git status`:
”Your branch is up to date with 'origin/main’.”
do you know that your branch may not actually be up to date with the `main` branch on the remote?
yes
mostly yes
no
what?
Poll ended at .
(i've been wondering if there's a world where it's possible to convince the folks who make git to change that message to add “... as of 5 minutes/3 days/6 years ago”, but I think it might be hard to implement)
emily dogmom@b0rk it COULD be? i think we can get it easily from mtime of .git/refs/remotes/<tracking remote>/<tracking branch>
@b0rk you can totally propose it to git at vger dot kernel dot org if you want, or i think you're already in the git discord, we'd be happy to advise through implementing a patch ;) ;)
@b0rk but i just tried out examining the mtime on .git/refs/origin/master before and after a fetch on my almost-always-stale laptop clone and it totally looked right
@nasamuffin ooh i didn’t know there was a git discord!
@nasamuffin the edge case i was worried about is that it looks like it doesn't update the mtime if you push (or fetch) and there were no updates?
(which makes sense because it wasn't modified, but the thing I _want_ is to know “we know that this is up to date as of X time” not “this is the last time there were new changes”)
@nasamuffin anyway I'll join the discord!
@b0rk sure, welcome! it's pretty new (~1yr) but more active than we expected it to be, for a bunch of crusty foss C devs
@b0rk yeah i saw that too unfortunately. that's pretty tricky, but we might be able to nudge the mtime on that ref anyway when we attempt the fetch and nothing happens 🤔
Olivier Mengué@b0rk @nasamuffin mtime is not much reliable anyway. Some filesystems do not record it or are specifically configured to not record it.
For example to optimize caching of Docker image layers mtime gets in the way (I don't remember the implementation details)
For example to optimize caching of Docker image layers mtime gets in the way (I don't remember the implementation details)