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

respond and close

Browse source
This commit is contained in:
Joey Hess 2017-02-07 15:18:45 -04:00
parent 27e89aeffc
commit d644316c94
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
2 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/bugs/annex_ignores_pushurl_and_uses_only_url_upon___34__copy_--to__34__.mdwn
View file

@ -79,3 +79,6 @@ So far we found the way to rectify it by providing value of pushurl as a remote.
lots
[[!meta author="yoh"]]
> [[done]] because there is already an annexUrl config to meet this need.
> --[[Joey]]

22
doc/bugs/annex_ignores_pushurl_and_uses_only_url_upon___34__copy_--to__34__/comment_1_92ea74beb2f8beb449769404a7f57a77._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-02-07T19:13:28Z"
content="""
Thing is, pushUrl is documented in git-push as "The <pushurl> is used for
pushes only.". And while git-annex is sending data to the remote,
that's not really the same as a push.
Following that logic, if git has a pullUrl, then git-annex should
use that for `git annex get`, since that's similar to a pull.
But then there are other operations git-annex does to remotes
that are similar to neither a push or a pull. And if git doesn't have a
pullUrl, then `git annex get` probably shouldn't use pushUrl, because
perhaps git will later get a pullUrl.
That's why annexUrl was added in 2011. Which is just used for all annex
operations.
So, I suggest you just set annexUrl at the same time you set pushUrl,
and be happy. ;)
"""]]