Make interactive form return a list for magit-init.
Fix quoting for default-value

The argument to default-value needs to be quoted
magit-rewrite-pending-diff: new function

This is a substitute for `magit-insert-pending-changes'.  The latter was
problematic because its implementation has not kept up with improvements
elsewhere.  I.e. the section it inserted was initially expanded and
worse when the user did collapse it, it kept being re-expanded on every
refresh.

Unfortunately there is no easy fix.  The only place where we can
currently prevent a diff from being expanded is in the "raw diff
washing" code.  The pending changes section, unlike staged and unstaged,
does not use raw washing.  It would be a major undertaking to teach the
raw washing how to deal with pending changes.  I don't want to do that
especially because having an additional raw washing cycle is a mistake
itself, which I have already fixed on the `next' branch.
Merge pull request #1315 from treese/fix-init

Make interactive form return a list for magit-init.
Merge pull request #1316 from lunaryorn/patch-1

Fix quoting for default-value
Merge branch 'master' into next

Conflicts:
	magit-key-mode.el
	magit.el
magit-svn-find-rev: bugfix

Don't create a section for no good reason whatsoever.
Also cleanup the other crap this function consisted of.
magit-stgit-show: just wrap around magit-show-commit
magit-stgit-wash-patch: use magit-insert
magit-stgit-wash-patch: fix use of magit-bind-match-strings
magit-stgit-wash-patch: make sure line matches
magit-insert-topgit-topic: fix use of magit-cmd-insert-section

This fixes c2c900aff8508f6882aa06e974c6d5413286abac.
magit-topgit.el: split into sections, rearrange

Split `magit-topgit.el' into the same sections (conceptually) in the
same order as in `magit-stgit.el'.

The new "Commands" section actually does not contain a single command,
but most of these functions should be commands.  Currently they only
hook into existing "action" commands, it would make sense to be able
to invoke them directly.

(Here is another TODO: `magit-topgit-wash-topic' has to be more like
other washers.  Someone who actually uses topgit should do that.)

The main reason the code in the "Mode" and "Topics Section" have
switched positions is because upcoming changes would otherwise cause
the byte-compiler to complain.
magit-insert-topgit-topics: make sure magit-topgit-mode is on
magit-define-section-jumper: absorb magit-goto-section-at-path

Merge `magit-goto-section-at-path' into its only caller
`magit-define-section-jumper'.  This fixes a bug as the former did
not return nil when the section could not be found, but the latter
expected it to do so.  Instead of just fixing that, merge because
the name `magit-goto-section-at-path' is to generic for a function
which only knows about sections that are direct children of the
root section.
magit-status-show-sequence-help: remove option
magit-insert-cherry-help-lines: don't abuse magit-insert-line-section
magit-insert-status-tags-line: use only colors, not verbs

Avoid uncertainty about whether the tag or the branch is the subject
when displaying the current and next tags in the header of the status
buffer, by using just colors to indicate which side has the additional
commits. Previously we used the verbs "ahead" and "behind", and which
one had to be used depended on whether the branch or the tag was
considered the subject of the "sentence".