mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

fix edge case where git-annex branch does not have config for enabled special remote

Browse source 
One way this could happen is cloning an empty special remote.
A later fetch would then fail.
This commit is contained in:
Joey Hess 2024-05-21 11:27:49 -04:00
parent 3e7324bbcb
commit b3d7ae51f0
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 13 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/todo/git-remote-annex.mdwn
View file

@ -12,9 +12,6 @@ This is implememented and working. Remaining todo list for it:
* Test incremental push edge cases involving checkprereq.
* Cloning a special remote with an empty manifest results in a repo where
git fetch fails, claiming the special remote is encrypted, when it's not.
* Cloning from an annex:: url with importtree=yes doesn't work
(with or without exporttree=yes). This is because the ContentIdentifier
db is not populated. It should be possible to work around this.