From: Joey Hess Date: Tue, 6 May 2025 15:54:06 +0000 (-0400) Subject: update X-Git-Tag: archive/raspbian/10.20251029-1+rpi1~1^2~7^2~188 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=13154f5cb24bfe055b6d617e78fee77da962e46a;p=git-annex.git update --- diff --git a/doc/todo/Recent_remote_activities/comment_2_d327c28a83eff83e071040c9fe79f739._comment b/doc/todo/Recent_remote_activities/comment_2_d327c28a83eff83e071040c9fe79f739._comment new file mode 100644 index 0000000000..2dfd51c639 --- /dev/null +++ b/doc/todo/Recent_remote_activities/comment_2_d327c28a83eff83e071040c9fe79f739._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2025-05-06T15:31:51Z" + content=""" +git grep for uuid is a good simple solution. + +Maybe `git-annex log --all` could be made to show all location log changes +for all keys. Then you could just grep that for the uuid to see what +changes have been happening to what files (if it mapped keys back to +current filenames when possible). Implementation would be `git log` +filtered to location log files, with `--raw` to get the diff, then +parsing the diff. + +There is already code that does something very similar in +Annex.RepoSize.diffBranchRepoSizes. And since that is already run by +`git-annex info`, it would be cheap to pull out a last activity date +for each repo at the same time as the repo's size, and have `git-annex +info` display it or use it in the other ways you suggest. + +The only wrinkle is that is an incremental diff since the +last time it was called, so would not include dates for repos that +have not changed since. So the dates would need to be cached +somewhere. +"""]]