highlights from next "What's cooking"

These have been merged for upcoming 1.7.9 recently:

 * jc/pull-signed-tag-doc (2012-01-17) 1 commit
  + pulling signed tag: add howto document

 * mh/maint-show-ref-doc (2012-01-13) 2 commits
   (merged to 'next' on 2012-01-16 at 8573f09)
  + git-show-ref doc: typeset regexp in fixed width font
  + git-show-ref: fix escaping in asciidoc source

 * nd/pathspec-recursion-cleanup (2012-01-16) 2 commits
   (merged to 'next' on 2012-01-16 at 0189264)
  + diff-index: enable recursive pathspec matching in unpack_trees
  + Document limited recursion pathspec matching with wildcards

 * tr/maint-word-diff-incomplete-line (2012-01-12) 1 commit
   (merged to 'next' on 2012-01-16 at 58ddaaf)
  + word-diff: ignore '\ No newline at eof' marker

 * jk/credentials (2012-01-16) 4 commits
   (merged to 'next' on 2012-01-16 at 2810b82)
  + credential-cache: ignore "connection refused" errors
   (merged to 'next' on 2012-01-16 at 1c6c94a)
  + unix-socket: do not let close() or chdir() clobber errno during cleanup
  + credential-cache: report more daemon connection errors
  + unix-socket: handle long socket pathnames


Also I updated the jc/pull-signed-tag topic that follows Linus's
suggestion to always spawn an editor when running "git merge" in an
interactive session.  The special-case environment variable has been
renamed to MERGE_AUTOEDIT, and scripts can set it to "no" when they start
to accept the autogenerated merge log message.  There is no plan to
encourage humans to keep using the historical behaviour, hence there is no
support for configuration variable (e.g. merge.autoedit) that can be set
to 'no'.