What's in git.git

The 'maint' and 'master' are at the same commit; a maintenance release v1.4.4.1 has been cut.

A handful enhancements that have been cooking in 'next' will start graduating to 'master' shortly; as usual, they won't be in the future v1.4.4.x maintenance series.

 * gitweb updates.

 * shortlog is now built-in.

 * enhance packed-refs file to optimize "show-ref -d".

 * retire merge-recursive-old.

 * shallow clone.

----------------------------------------------------------------

* The 'next' branch, in addition to what are in 'master', has these.

   Andy Parkins (2):
      Improve git-prune -n output
      Add support to git-branch to show local and remote branches

   Jakub Narebski (7):
      gitweb: Protect against possible warning in git_commitdiff
      gitweb: Buffer diff header to deal with split patches + git_patchset_body refactoring
      gitweb: Default to $hash_base or HEAD for $hash in "commit" and "commitdiff"
      gitweb: New improved formatting of chunk header in diff
      gitweb: Add an option to href() to return full URL
      gitweb: Refactor feed generation, make output prettier, add Atom feed
      gitweb: Finish restoring "blob" links in git_difftree_body

   Johannes Schindelin (5):
      Build in shortlog
      shortlog: do not crash on parsing "[PATCH"
      shortlog: read mailmap from ./.mailmap again
      shortlog: handle email addresses case-insensitively
      shortlog: fix "-n"

   Junio C Hamano (9):
      upload-pack: stop the other side when they have more roots than we do.
      adjust_shared_perm: chmod() only when needed.
      apply --numstat: mark binary diffstat with - -, not 0 0
      pack-objects: tweak "do not even attempt delta" heuristics
      Store peeled refs in packed-refs file.
      remove merge-recursive-old
      git-merge: make it usable as the first class UI
      git-diff/git-apply: make diff output a bit friendlier to GNU patch (part 2)
      Store peeled refs in packed-refs (take 2).

   Nicolas Pitre (1):
      builtin git-shortlog is broken

* The 'pu' branch, in addition, has these.

   Alexandre Julliard (1):
      Shallow clone: do not ignore shallowness when following tags

   Johannes Schindelin (5):
      upload-pack: no longer call rev-list
      support fetching into a shallow repository
      allow cloning a repository "shallowly"
      allow deepening of a shallow repository
      add tests for shallow stuff

   Junio C Hamano (10):
      git-commit: show --summary after successful commit.
      para-walk: walk n trees, index and working tree in parallel
      rev-list --left-right
      merge: allow merging into a yet-to-be-born branch.
      blame: --show-stats for easier optimization work.
      gitweb: steal loadavg throttle from kernel.org
      We should make sure that the protocol is still extensible.
      Why does it mean we do not have to register shallow if we have one?
      Why didn't we mark want_obj as ~UNINTERESTING in the old code?
      shallow clone: unparse and reparse an unshallowed commit