]> git.madduck.net Git - code/vcsh.git/commitdiff

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

README.md: Better wording
authorRichard Hartmann <richih.mailinglist@gmail.com>
Sun, 9 Jun 2013 11:37:29 +0000 (13:37 +0200)
committerRichard Hartmann <richih.mailinglist@gmail.com>
Sun, 9 Jun 2013 11:37:29 +0000 (13:37 +0200)
README.md

index 78dca61594da1f27fde0ab981a89a4d89eec454a..302411267c164b8e47dd1de90e648cfeba9d5312 100644 (file)
--- a/README.md
+++ b/README.md
@@ -52,7 +52,7 @@ community around the general idea of version controlling your (digital) life.
 directory. They all maintain their working trees without clobbering each other
 or interfering otherwise. By default, all git repositories maintained via
 `vcsh` are stored in `$HOME` but you can override this setting if you want to.
 directory. They all maintain their working trees without clobbering each other
 or interfering otherwise. By default, all git repositories maintained via
 `vcsh` are stored in `$HOME` but you can override this setting if you want to.
-All that means that you can have one repository per application or application
+All this means that you can have one repository per application or application
 family, i.e. `zsh`, `vim`, `ssh`, etc. This, in turn, allows you to clone
 custom sets of configurations onto different machines or even for different
 users; picking and mixing which configurations you want to use where.
 family, i.e. `zsh`, `vim`, `ssh`, etc. This, in turn, allows you to clone
 custom sets of configurations onto different machines or even for different
 users; picking and mixing which configurations you want to use where.