magit-blame-{prev,next}-chunk

Always move to the previous/next chunk from *point*.  Previously that
was done interactively but non-interactively the POS argument had to
be provided.  Which is wrong for two reasons:  we did not use it
non-interactively, so even if this was a good idea in the first place
it would be of no use.  And then there is no reason for a movement
command to be have "move to next thing from point, except when I tell
you to move from somewhere else".  If one wants that - especially in
non-interactive use, one can just go to that other place *before*
going to the next thing,
magit-run-git-gui-blame: fix when linenum is missing

We can't guarantee that we'll always know which line number
we want to center the `git gui blame' process around.  This
fixes an error caused by attempting to pass nil as one of
the arguments to `start-file-process'.

Message-by: Adam Spiers <github@adamspiers.org> :-)
Reported-by: Adam Spiers <github@adamspiers.org>

Or

  "Make that lazy ass lisp reader do some work."
don't require feature when it cannot possible not be loaded yet

 (eval-after-load 'dired-x ; <--.
   '(...                   ;    |
-    (require 'dired-x)    ; <--'
     ...))

What more can I say? ;-)
magit-version: fix comment
fix remote branch names with slashes
Merge pull request #952 from finalpatch/master

fix remote branch names with slashes
magit-get-tracked-branch: prettify
autoload commands that are useful outside a magit buffer

Add autoload cookies for commands that can be used when the current
buffer isn't a Magit buffer.
move bindings from magit-status-mode-map to magit-mode-map

Move some key bindings that do *not* depend on the existence certain
items (which might not exist in non-status buffers) from
`magit-status-mode-map' to `magit-mode-map'.
move hacks inside section "Branch Manager Mode" to its end

Inside the section "Branch Manager Mode" move a group of utilities to
the end of the section.  These utilities are only used in this section
and have two problems, they are not quiet sufficient and they should
be generalized so that they can also be used elsewhere.
split magit-wash-branch-line-re from magit-wash-branch-line

Extract the regular expression previously embedded inside the
function `magit-wash-branch-line' and store it in a constant
`magit-wash-branch-line-re' (like we do for other such regexps).
magit-wash-branch-line-re: cleanup
magit-wash-remote-branches-group: fix whitespace
magit-change-what-branch-tracks: use a simpler prompt
magit-change-what-branch-tracks: sorter names for internal variables
magit-wash-log: use author/date overlay only with oneline style

Do not display the author/date overlay for log style `long', only
for `oneline'.  When the style is `long' then displaying the overlay
fails *and* it is unnecessary because the author information is
already displayed in another fashion.
magit-wash-log: give the code some room to breath
magit-wash-log: remove an unnecessary let-bound variable

Instead of binding USE-AUTHOR-DATE to the value of

  (eq style 'oneline)

just perform that test twice.  That is cheap enough; it might be even
cheaper than a variable binding.  Regardless, I think it improves
readability a lot.
magit-default-rev: always respect NO-TRIM argument

Previously this was only done when a commit could be found at point but
not when we had to use `magit-guess-branch'.
merge magit-wash-untracked-file into magit-wash-untracked-files