diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-03-18 16:13:54 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-03-18 16:13:54 -0400 |
| commit | efd555848d042450d867761799ebd1b23459ea4e (patch) | |
| tree | fd06f87aecfe4963e4729519ed24d3439f559db1 /doc/walkthrough | |
| parent | b7ed29f3c07c7025c203813e4ecc5b6c6908279f (diff) | |
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.
Diffstat (limited to 'doc/walkthrough')
| -rw-r--r-- | doc/walkthrough/adding_a_remote.mdwn | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/walkthrough/adding_a_remote.mdwn b/doc/walkthrough/adding_a_remote.mdwn index 013ac5110..be8e8e7fe 100644 --- a/doc/walkthrough/adding_a_remote.mdwn +++ b/doc/walkthrough/adding_a_remote.mdwn @@ -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. |