correct spelling mistakes

A few spelling fixes for the git-annex devblog.
This commit is contained in:
Edward Betts 2017-10-26 07:52:20 +01:00 committed by Joey Hess
parent 50c0fb7336
commit 3a927a0345
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 3 additions and 3 deletions

View file

@ -7,7 +7,7 @@ suites should not do. So, I took a detour..
Support for `GIT_SSH` and `GIT_SSH_COMMAND` has been requested before for
various reasons. So I implemented that, which took 4 hours. (With one
little possible compatability caveat, since git-annex needs to pass the -n
little possible compatibility caveat, since git-annex needs to pass the -n
parameter to ssh sometimes, and git's interface doesn't allow for such a
parameter.)

View file

@ -10,7 +10,7 @@ run to vary what remotes are used depending on eg, what network it's on.
Also, I took a look at the external special remote protocol, and noticed
two problems with it. First, keys with spaces in their names can't be used
with it. This only affects the WORM backend, and it seems noone has ever
with it. This only affects the WORM backend, and it seems no one has ever
run into the problem. Rather than complicate the implementation of external
special remotes, I decided to deprecate having spaces in key names. Which
is just asking for trouble anyway. So now there's a nice error message, and

View file

@ -8,7 +8,7 @@ So, I decided to add a remote method to delete a directory, and make
git-annex keep track of when a directory in an export is empty, and delete
it. While it does complicate the design some to need to do this, that seems
better than complicating the implementation of remotes like webdav. And
some remotes may not have a `rmdir(2)` equivilant or a way to check if a
some remotes may not have a `rmdir(2)` equivalent or a way to check if a
directory is empty.
Spent most of today implementing that, including some rather hairy