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

refuse to fetch from a remote that has no manifest

Browse source 
Otherwise, it can be confusing to clone from a wrong url, since it fails
to download a manifest and so appears as if the remote exists but is empty.

Sponsored-by: Jack Hill on Patreon
This commit is contained in:
Joey Hess 2024-05-13 09:47:21 -04:00
parent 424afe46d7
commit 3f848564ac
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 31 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -28,11 +28,6 @@ This is implememented and working. Remaining todo list for it:
stored in the repo. Chicken and egg problem cloning from
such a remote. Maybe allow advanced users to force it?
* When the remote has no manifest, a pull from it should fail,
while a push should succeed. Otherwise, it can be confusing
to clone from a wrong url, since it fails to download
a manifest and so appears as if the remote is empty.
* Improve recovery from interrupted push by using outManifest to clean up
after it. (Requires populating outManifest.)