There are other ways to do this, but this seems to be the most commonly
used and easiest way to get the job done. Alternate methods could be
added but at least having this one will alert folks that using this on
OSX is an option.

Since myrepos is so strongly recommended, included it in the distro
specific install instructions. Refactor the Arch Linux instructions
to better reflect most common usage.

Encourage the use of the stable packages per disro norms. The devel
packages can be used but they trigger full git clones in many AUR
helpers and are generally a pain if you don't specifically want them for
something. Mention the devel package but update the URLs to point to
the one that uses the normal packaging system.

The `mr` utilily is now called myrepos upstream and they have a new
website address. Update the links in the readme, reflect the new name
of the project where appropriate, and fix the copy surrounding its
introdiction. The actual command is still `mr`.

GitHub: fixes RichiH/vcsh#105

Conflicts:
	vcsh

Fix typo $XDH_CONFIG_HOME -> $XDG_CONFIG_HOME

If `git foo` exits 13, it would be prudent for vcsh to exit 13, as well.
Start with support for `vcsh pull`.

GitHub: fixes RichiH/vcsh#104

Add hooks to allow fancy merge handling

Cloning a repo over an existing set of files would usually
cause a merge conflict that aborts the process and requires
manual intervention. This pair of hooks handles that case
by manually moving the extant objects out of the way,
completing the checktout, then restoring them to their
original places. The resulting state is a set of unstaged
local changes.

These hooks before and after the actual checkout process
will enable a pair of hook scripts to automatically handle
conflicts and potentially allow the checkout of repositories
over existing file sets

By replacing the "for" loop with a "while" loop, it is easy to read
line-oriented output without worrying about spaces. However, now the
loop executes in a subshell, and VCSH_CONFLICT won't be available in
the parent shell. In this case, a trivial, portable solution is to
have the comparison as the last command in the subshell.

`vcsh clone` does:

    VCSH_REPO_NAME=$(basename "${GIT_REMOTE}" .git)

Typically, most remote paths will have a non-empty directory component,
so using basename works well in all common cases. However, when doing
something like:

    % vcsh clone example.org:repo.git

VCSH_REPO_NAME will be set to "example.org:repo" instead of "repo". This
also happens when using url.<x>.insteadOf, à-la:

    % vcsh clone v:repo

Stripping everything up to the first colon in the remote URL fixes the
issue.

N.B.: remote URLs with protocol (e.g. http://, git://, or ssh://) do
not exhibit this problem, and are unaffected by this change.

Conflicts:
	vcsh

Configurations and other dotdir content may be highly confidential.

Ensure we're not leaking/exposing information by making vcsh
repositories user-accessible, only.

Thanks to Enrico Zini for realizing this was a problem.

Opening Vim in $PWD without a file name (think scratch pad) will open
.swp, which is not matched by *.swp

Add Gentoo installation in README

2650689d introduced a bug:
If we are using a template, GNU mktemp will use PWD instead of $TMPDIR