bind j instead of M-g to magit-jump-to-diffstats

Do so in the two relevant keymaps `magit-commit-mode-map' and
`magit-diff-mode-map'.  In other maps `j' is bound to the related
`magit-section-jump-map'.
magit.el: explicitly set coding system to utf-8

Unlike the other libraries `magit.el' contains some non-ascii
characters.  Usually Emacs used utf-8 if nothing else is specified
but for some language environments this does not seem to be the case.
magit-mode-refresh-buffer: don't fiddle with window point

See #1451.
magit-locate-emacsclient: kludge for multi-arch Emacs for Mac OS X
magit-commit-add-log: Use symbol boundary in function name REGEXP

Use symbol boundary instead of word boundary in function name REGEXP. This is
because using word boundary causes partial function name being matched. As an
example, let's say we have two diff hunks, one in the function `foo' and the
other in `foo-bar'. When the word boundary REGEXP is used, the REGEXP matches
both function name `foo' and `foo-bar', which will prevent
`magit-commit-add-log' from adding a log entry for function `foo-bar' if an
entry for function `foo' already exist.
Add a defcustom for `magit-status-mode-hook'.

This will allow users to customize it and extension packages, such as
magit-filenotify, to use `custom-add-option' to add themselves as option
to it.
Add `magit-load-config-extensions' option to `magit-mode-hook'.

This will make it easier and more noticeable when customizing magit.
Add options for stgit, svn, topgit to `magit-mode-hook'.

This will make them more noticeable when customizing magit and easier to
enable.
Merge pull request #1455 from YorkZ/bug-fix

magit-commit-add-log: Use symbol boundary in function name REGEXP
Merge pull request #1456 from ruediger/customhookoptions

Provide options for `magit-mode-hook`
magit-list-repos*: skip inaccessible directories

Fixes #1463.
avoid needlessly connecting to unrelated tramp remotes

In `magit-save-buffers-predicate-tree-only' avoid needlessly connecting
to unrelated tramp remotes by first checking whether the absolute path
to the top-level of the current directory is a prefix of
`buffer-file-name'.  Only if that is so check whether `buffer-file-name'
is actually directly in that repository (it may also be part of a
submodule or other nested repository.

Fixes #1473.

Suggested-by: Ryan C. Thompson <rct@thompsonclan.org>
magit-checkout: remove "tracking branch confusion"

This is a backport of 9af9551470d1f10295ebd0aa5c1fac079a829e1d from
next, but where that completely removes the ability to create a local
branch whose upstream is a remote branch when using `magit-checkout',
this only removes the unnecessary complications that resulted from a
misunderstandings of what "tracking branches" are.

Similar functionality might later be restored on next.

Also see #1476.
magit-save-buffers-predicate-tree-only: bugfix

This function might end up being called outside a repository (because it
is used carelessly, see next branch for a better approach) so we have to
make sure it does not try anything stupid in that case.  Fixes #1499.
magit-process-finish: bind message search correctly

Limit the search for the error message to the section of the current
section, as intended.  Fixes #1498.
magit-delete-branch: do not create master branch

Fixes #1501.
README.md: update links

* Gittip was renamed to Gratipay.
* Against all odds we made a 1.2.1 maintenance release.
* To help hyperlink-challenged users the Known Issues
  have been merged into the FAQ.
README.md: wording changes
magit-run-git-gui-blame: fix when linenum is missing

2eb34da broke magit-run-git-gui-blame by erroneously changing the
argument to magit-file-relative-name to be a directory.  This prevented
the linenum argument from being properly populated.
Merge pull request #1530 from aspiers/fix-git-gui-blame

magit-run-git-gui-blame: fix when linenum is missing