rename status to info, and update docs
This commit is contained in:
parent
4eeebf162f
commit
eed2ed4fdb
8 changed files with 27 additions and 24 deletions
|
@ -25,7 +25,7 @@ Now you can run normal annex operations, as long as the port forwarding shell is
|
|||
|
||||
git annex sync
|
||||
git annex get on-the-go some/big/file
|
||||
git annex status
|
||||
git annex info
|
||||
|
||||
You can add more computers by repeating with a different port, e.g. 2202 or 2203 (or any other).
|
||||
|
||||
|
|
|
@ -31,7 +31,7 @@ On `angela`, we want to synchronise the git annex metadata with `marcos`. We nee
|
|||
git init
|
||||
git remote add marcos marcos.example.com:/srv/mp3
|
||||
git fetch marcos
|
||||
git annex status # this should display the two repos
|
||||
git annex info # this should display the two repos
|
||||
git annex add .
|
||||
|
||||
This will, again, checksum all files and add them to git annex. Once that is done, you can verify that the files are really the same as marcos with `whereis`:
|
||||
|
|
|
@ -4,6 +4,6 @@
|
|||
subject="comment 1"
|
||||
date="2013-07-12T19:36:28Z"
|
||||
content="""
|
||||
Ah, I just found that git annex status can do the same :)
|
||||
Ah, I just found that git annex info can do the same :)
|
||||
Disregard this.
|
||||
"""]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue