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
|
@ -40,7 +40,7 @@ everyday problem for an average user.
|
|||
>
|
||||
> Also, the assistant sets up it *own* .ssh/config hostname alias,
|
||||
> in order to make it use the special ssh key that it generates for the host.
|
||||
> So that is not compatable with using a ssh host alias you've set up.
|
||||
> So that is not compatible with using a ssh host alias you've set up.
|
||||
> Even if it knew about your alias, it would set up a new hostname alias, and
|
||||
> whatever machinery you have to update the alias would not work.
|
||||
>
|
||||
|
|
|
@ -17,7 +17,7 @@ that almost everything uses. But in its favor:
|
|||
|
||||
* --sameas already relies on special remotes using the same path form, and so
|
||||
it seems we're going to end up documenting which special remotes are
|
||||
compatable. That information could even be encoded in the remotes and
|
||||
compatible. That information could even be encoded in the remotes and
|
||||
git-annex sanity check uses of --sameas.
|
||||
|
||||
Perhaps --sameas is a slippery slope and this should not continue down it,
|
||||
|
|
|
@ -21,7 +21,7 @@ same encrypted special remote.
|
|||
|
||||
Update: That's implemented now, when annex.shared-sop-command is configured
|
||||
it will be used for encryption=shared special remotes. It interoperates
|
||||
fine with using gpg, as long as the sop command uses a compatable profile
|
||||
fine with using gpg, as long as the sop command uses a compatible profile
|
||||
(setting annex.shared-sop-profile = rfc4880 is probably a good idea).
|
||||
|
||||
Leaving this todo open because there are other encryption schemes than
|
||||
|
|
|
@ -11,7 +11,7 @@ Eg, to use Sequoia's sqpop:
|
|||
git config annex.shared-sop-command sqop
|
||||
|
||||
That fully interoperates with gpg, though it's probably a good idea
|
||||
to specify an enryption profile that is backwards compatable if interop
|
||||
to specify an enryption profile that is backwards compatible if interop
|
||||
is a concern. Eg:
|
||||
|
||||
git config annex.shared-sop-profile rfc4880
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue