diff options
| author |  Yaroslav Halchenko <debian@onerussian.com> | 2016-05-24 17:23:55 -0400 |
|---|---|---|
| committer |  Joey Hess <joeyh@joeyh.name> | 2016-05-27 15:26:34 -0400 |
| commit | 42f9a3f410df7853a020384ea3a3c2ce26a3e56d (patch) | |
| tree | b8dc0428ec036bd2bff1682e6e61c7320402f520 | |
| parent | 74a94ddfac2940575721826911dd8b15a74011e5 (diff) | |
minor typos in devblog
| -rw-r--r-- | doc/devblog/day_394__implicit_vs_explicit.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/devblog/day_394__implicit_vs_explicit.mdwn b/doc/devblog/day_394__implicit_vs_explicit.mdwn index 681ef9211..300ac4c57 100644 --- a/doc/devblog/day_394__implicit_vs_explicit.mdwn +++ b/doc/devblog/day_394__implicit_vs_explicit.mdwn @@ -1,7 +1,7 @@ git-annex has always balanced implicit and explicit behavior. -Enabling a git reository to be used with git-annex needs an explicit init, +Enabling a git repository to be used with git-annex needs an explicit init, to avoid foot-shooting; but a clone of a repository that is already -using git-annex will be implicitally initialized. Git remotes implicitly +using git-annex will be implicitly initialized. Git remotes implicitly are checked to see if they use git-annex, so the user can immediately follow `git remote add` with `git annex get` to get files from it. |