sync: Fix parsing of gcrypt::rsync:// urls that use a relative path
authorJoey Hess <joeyh@joeyh.name>
Thu, 23 Mar 2023 19:19:04 +0000 (15:19 -0400)
committerJoey Hess <joeyh@joeyh.name>
Thu, 23 Mar 2023 19:20:00 +0000 (15:20 -0400)
commita0badc5069f3b86cc283a181cc38ff31954280a8
tree7981f79ff5c9fd41a27efb355160c1727551cd8e
parent0e18bf029e6721b1c9665b0fbea6d281b9d65f7c
sync: Fix parsing of gcrypt:: urls that use a relative path

Such an url is not valid; parseURI will fail on it. But git-annex doesn't
actually need to parse the url, because all it needs to do to support
syncing with it is know that it's not a local path, and use git pull and
push.

(Note that there is no good reason for the user to use such an url. An
absolute url is valid and I patched git-remote-gcrypt to support them
years ago. Still, users gonna do anything that tools allow, and
git-remote-gcrypt still supports them.)

Sponsored-by: Jack Hill on Patreon
12 files changed:
Assistant/WebApp/Configurators/Edit.hs
Assistant/WebApp/Gpg.hs
Assistant/WebApp/RepoList.hs
CHANGELOG
Command/Sync.hs
Git/Construct.hs
Git/GCrypt.hs
Git/Remote.hs
Remote/GCrypt.hs
Remote/Git.hs
Remote/GitLFS.hs
doc/bugs/gcrypt_remotes_using_relative_paths.mdwn