remove bad information
You do not need to pull from a remote to make git-annex aware of it. Pulling only makes git know about remote/master branches, but git-annex does not care about that. When git-annex encounters a remote in .git/config that has no recorded annex.uuid, it connects to it to get the uuid automatically, and will immediately start using it. A later part of this walkthrough shows how to pull from a remote in order to get its location tracking info, so that git-annex can retrieve files from it. That's the right place to document the need to pull from a remote periodically.
This commit is contained in:
parent
b7ed29f3c0
commit
efd555848d
1 changed files with 0 additions and 2 deletions
|
@ -17,5 +17,3 @@ of the new repository created on the USB drive.
|
|||
Notice that both repos are set up as remotes of one another. This lets
|
||||
either get annexed files from the other. You'll want to do that even
|
||||
if you are using git in a more centralized fashion.
|
||||
|
||||
Note that you need to pull from the new remote at least once to make your local annex aware of the remote annex.
|
||||
|
|
Loading…
Add table
Reference in a new issue