comment (and a new example)
This commit is contained in:
parent
47f92409f2
commit
1e580a30be
2 changed files with 23 additions and 0 deletions
|
@ -5,8 +5,15 @@ It would allow a workflow like eg:
|
|||
|
||||
edit foo
|
||||
git-annex add foo
|
||||
git commit -m new\ foo
|
||||
git-annex oldkeys foo | git-annex move --batch-keys --to bar
|
||||
|
||||
Or this, to send someone the current version of a file, and also all old
|
||||
versions:
|
||||
|
||||
git-annex copy foo --to baz
|
||||
git-annex oldkeys foo | git-annex copy --to baz
|
||||
|
||||
Or like this:
|
||||
|
||||
git-annex oldkeys foo | git-annex get --batch-keys
|
||||
|
|
|
@ -0,0 +1,16 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 3"""
|
||||
date="2023-08-22T19:02:26Z"
|
||||
content="""
|
||||
This is certainly adjacent to unused, but it's not quite the same.
|
||||
|
||||
I think users will generally want this to list keys even if they are
|
||||
still used by some other files in the tree besides the files that they
|
||||
are querying. (There may be cases where that is not desirable of course,
|
||||
but at least 3 of the 4 examples I came up with seem desirable to operate
|
||||
that way.)
|
||||
|
||||
And a key listed by this command might be used by other branches, so unused
|
||||
would not list it.
|
||||
"""]]
|
Loading…
Reference in a new issue