Fix compatable typo (yet to add to codespell)
=== Do not change lines below === { "chain": [], "cmd": "git-sedi compatable compatible", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^
This commit is contained in:
parent
87e2ae2014
commit
9c2ab31549
12 changed files with 12 additions and 12 deletions
|
@ -13,7 +13,7 @@ about the new remote yet, and crashed (and was restarted knowing about it,
|
|||
so successfully sent any other files). So got sidetracked on fixing that.
|
||||
|
||||
Also did some work to make the gpg bundled with git-annex on OSX be
|
||||
compatable with the config files written by MacGPG. At first I was going to
|
||||
compatible with the config files written by MacGPG. At first I was going to
|
||||
hack it to not crash on the options it didn't support, but it turned out
|
||||
that upgrading to version 1.4.14 actually fixed the problem that was making
|
||||
it build without support for DNS.
|
||||
|
|
|
@ -40,7 +40,7 @@ complicate it, and the hidden service side would need to listen on a unix
|
|||
socket, instead of the regular http port. It might be worth it to use http
|
||||
for tor, if it could be reused for git-annex http servers not on the tor
|
||||
network. But, then I'd have to make the http server support git pull and
|
||||
push over http in a way that's compatable with how git uses http, including
|
||||
push over http in a way that's compatible with how git uses http, including
|
||||
authentication. Which is a whole nother ball of complexity. So, I'm leaning
|
||||
instead to using a simple custom protocol something like:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue