mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2023-08-22 15:01:43 -04:00
commit 47f92409f2
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 26 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/todo/command_to_list_keys_for_old_versions_of_files/comment_1_43c11d9467b4d4460aa97bfb88b4896f._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="nobodyinperson"
avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
subject="Oh yes please 🤩"
date="2023-08-22T16:48:58Z"
content="""
`unusedkeys` would be consistently named with `git annex unused`. Would it make sense to teach `git annex unused` that? It could be taught to accept paths as arguments (it doesn't currently, right?) and then only operate on those to find old versions. Then no new command is necessary and people already know `unused`. The workflow would be:
```
# two-step
git annex unused file.txt
git annex move --unused --to there
# new option to only list keys for further scripting
git annex unused --onlykeys file.txt | xargs ...
# maybe --batch is a better name 🤷
```
"""]]

8
doc/todo/command_to_list_keys_for_old_versions_of_files/comment_2_5062a0f8b57fdebf74fef8a65ac0a0b2._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="nobodyinperson"
avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
subject="comment 2"
date="2023-08-22T17:57:45Z"
content="""
Or better: make `git annex unused` accept the common matching options. Then `git annex unused --include=myfile.txt` can be used for the same effect.
"""]]