oldkeys: check associated files by default and add --unchecked
Removed the prior code that checked for keys used by current versions of the files being acted on. It is redundant with the associated files check (so long as the associated files database is always up-to-date, which reconcileStaged should accomplish). Sponsored-by: Luke T. Shumaker on Patreon
This commit is contained in:
parent
1e580a30be
commit
49b97b0675
2 changed files with 34 additions and 47 deletions
|
@ -15,14 +15,21 @@ The output from this command can be piped into a command like
|
|||
|
||||
The keys are listed in order from newest to oldest.
|
||||
|
||||
When listing old keys for a directory, it will include the most recent
|
||||
key used by deleted files (but not by renamed files).
|
||||
|
||||
Note that the listed keys may still be used by other files in the
|
||||
repository.
|
||||
When listing old keys for a directory, it will include keys used by deleted
|
||||
files that were in that directory in past commits.
|
||||
|
||||
# OPTIONS
|
||||
|
||||
* --unchecked
|
||||
|
||||
By default this command does not list a key that is also used by any
|
||||
file in the currently checked out branch. This option makes it also
|
||||
list such keys.
|
||||
|
||||
The default behavior avoids surprises when dropping listed keys.
|
||||
This option can be useful when eg copying all old versions of a file to a
|
||||
remote.
|
||||
|
||||
* --revision-range=value
|
||||
|
||||
Only list old keys used in the specified range of revisions.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue