* magit-key-mode.el (magit-key-mode-add-group): add missing arguments
  list when creating new group.
Merge pull request #1347 from jtatarik/fix_add_group_arguments

magit-key-mode-add-group: add missing arguments list when creating new group
magit.text: mentioned that staging only works from status buffer
Package-Requires: add emacs-23.2
magit-process-setup: never collapse the section

Despite the face being used, too many users fail to realize that the
lines in the process buffer are sections and thus never try to show
the output by pressing TAB.

On the `next' branch this is being countered by creating all sections
expanded and only collapsing a section once the command returned
successfully, see 160ed937ff28bcf0c9fc84763376e7c88f3d836a.  That hasn't
made it to `master' yet, where we are doing something less reasonable.
So for now change `magit-process-setup' to never automatically collapse
a section.
.travis.yml: update dependency urls
magit-read-gpg-secret-key: properly use history variable
Revert "Package-Requires: add emacs-23.2"

This reverts commit 3f2f81b347bff884ad4759ed4c8b12c204ce75e0.

No version of `package.el' which works with Emacs 23.x
understands the "emacs" virtual package.  See issue #1369.
magit-read-gpg-secret-key: don't require match

Let the user exit with any input.  This allows selecting a subkey,
even though we don't offer such keys for completion.
magit-diff-highlight-whitespace: use lazy match
Lazy match should be used to find trailing spaces.
Merge pull request #1373 from shigi/trailing-spaces

magit-diff-highlight-whitespace: use lazy match
magit-git-executable: except on windows, use just the name

Since f0186c88732e543d9487082405685fa0a2688b70 `magit-git-executable'
was set to the full path to the executable, which becomes problematic
when connecting to a remote repository using Tramp and the executable
is not installed in the identical location on that system.

On Windows keep using the full path, because here multiple "git.***"
are installed and it makes a big difference which is used.  I would
much rather have a handful of Windows users report that they cannot
use Magit remotely than to have many more users complain that "Magit
is nice, but soooooooo slow on Windows".

We could use different variable for local and tramp Git, I suppose.
But the proper way of testing that is `file-remote-p', and that is
to expensive to run over and over again.  And I don't like caching.
deal with yet another way Emacs can be installed on OS X
fix 973a5ab06a55e0b8779be91968d32a92851b6f68
magit-svn-find-rev: fix issue #1404

`magit-show-commit' expects a string not a section.
try harder to locate a suitable emacsclient executable

Improve how the default value of `magit-emacsclient-executable' is
determined.  If we fail to do so, show a warning.

We determine whether an emacsclient executable is compatible with the
current Emacs instance by comparing its version with `emacs-version'.
The versions don't have to match exactly, but at least the major part
has to do so.

This commit changes how an executable's version is determined.
Previously we simply used the version suffix of the executable.
Unfortunately when Emacs is installed manually, then the emacsclient
executable usually does not have a version suffix, and so we did fall
back to the suffix-less executable which comes first on `exec-path',
which is a lottery.

Now we use `emacsclient --version' to determine the version, and the
order in which version-suffix-less emacsclient executable appear on
the `exec-path' therefor no longer matters.
Merge branch 'locate-emacsclient'
fix last commit
magit-locate-emacsclient: quote value

Also remove an unused variable.
AUTHORS.md: update list of contributors