Added a comment: one more question
This commit is contained in:
parent
2dedf68e53
commit
144500f19d
1 changed files with 12 additions and 0 deletions
|
@ -0,0 +1,12 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="imlew"
|
||||||
|
avatar="http://cdn.libravatar.org/avatar/23858c3eed3c3ea9e21522f4c999f1ed"
|
||||||
|
subject="one more question"
|
||||||
|
date="2023-11-17T08:23:32Z"
|
||||||
|
content="""
|
||||||
|
I'm not sure if this is caused by the disk's repo being bare, but after I have `git annex move`d a file there I still need to run `git annex sync` in the local source repo before I can find or copy the file to a third repo (in this case a second repo on my laptop).
|
||||||
|
|
||||||
|
This is a little confusing because it seems the bare repo on the disk doesn't know it has the files that have been moved to it.
|
||||||
|
|
||||||
|
Is this because it is bare, am I doing something wrong or why doesn't `git annex move` result in the target knowing that it has a given file?
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue