response
This commit is contained in:
parent
da6d69f691
commit
96cff22d8d
2 changed files with 18 additions and 0 deletions
|
@ -20,6 +20,10 @@ For example:
|
|||
62b39bbe-4149-11e0-af01-bb89245a1e61 -- usb drive [here]
|
||||
7570b02e-15e9-11e0-adf0-9f3f94cb2eaa -- backup drive
|
||||
|
||||
Note that this command does not contact remotes to verify if they still
|
||||
have the content of files. It only reports on the last information that was
|
||||
received from remotes.
|
||||
|
||||
# OPTIONS
|
||||
|
||||
* file matching options
|
||||
|
|
|
@ -0,0 +1,14 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 2"""
|
||||
date="2018-09-24T15:33:02Z"
|
||||
content="""
|
||||
I've added a para above. Note that this is a wiki, and you can edit it
|
||||
too!
|
||||
|
||||
Showing the timestamp of when the file was added to the remote could be
|
||||
done; git-annex does not track the last time it verified content was on a
|
||||
remote and tracking that would bloat the git-annex branch. I don't think
|
||||
displaying a very old timestamp for data at rest would give the right
|
||||
impression though.
|
||||
"""]]
|
Loading…
Reference in a new issue