update
This commit is contained in:
parent
2bf3addf49
commit
faf55ac2b7
1 changed files with 2 additions and 3 deletions
|
@ -1,8 +1,7 @@
|
||||||
git-annex keeps track of in which repositories it last saw a file's content.
|
git-annex keeps track of in which repositories it last saw a file's content.
|
||||||
This location tracking information is stored in the git-annex branch.
|
This location tracking information is stored in the git-annex branch.
|
||||||
Repositories record their UUID and the date when they get or drop
|
Repositories record their UUID and the date when they get or drop
|
||||||
a file's content. (Git is configured to use a union merge for this file,
|
a file's content.
|
||||||
so the lines may be in arbitrary order, but it will never conflict.)
|
|
||||||
|
|
||||||
This location tracking information is useful if you have multiple
|
This location tracking information is useful if you have multiple
|
||||||
repositories, and not all are always accessible. For example, perhaps one
|
repositories, and not all are always accessible. For example, perhaps one
|
||||||
|
@ -10,7 +9,7 @@ is on a home file server, and you are away from home. Then git-annex can
|
||||||
tell you what git remote it needs access to in order to get a file:
|
tell you what git remote it needs access to in order to get a file:
|
||||||
|
|
||||||
# git annex get myfile
|
# git annex get myfile
|
||||||
get myfile(not available)
|
get myfile (not available)
|
||||||
I was unable to access these remotes: home
|
I was unable to access these remotes: home
|
||||||
|
|
||||||
Another way the location tracking comes in handy is if you put repositories
|
Another way the location tracking comes in handy is if you put repositories
|
||||||
|
|
Loading…
Reference in a new issue