Log message:
Clarify DESCRs to explain what is in which package.  It's particularly
unexpected that man pages, which most people would want, are split,
while tk and python dependencies, expected to be the first to be
jettisoned on small systems, are in the base package.

Log message:
Changes 1.7.7.2:
* We used to drop error messages from libcurl on certain kinds of
  errors.
* Error report from smart HTTP transport, when the connection was
  broken in the middle of a transfer, showed a useless message on
  a corrupt packet.
* "git fetch --prune" was unsafe when used with refspecs from the
  command line.
* The attribute mechanism did not use case insensitive match when
  core.ignorecase was set.
* "git bisect" did not notice when it failed to update the working tree
  to the next commit to be tested.
* "git config --bool --get-regexp" failed to separate the variable name
  and its value "true" when the variable is defined without "= \ 
true".
* "git remote rename $a $b" were not careful to match the remote name
  against $a (i.e. source side of the remote nickname).
* "git mergetool" did not use its arguments as pathspec, but as a path to
  the file that may not even have any conflict.
* "git diff --[num]stat" used to use the number of lines of context
  different from the default, potentially giving different results from
  "git diff | diffstat" and confusing the users.
* "git pull" and "git rebase" did not work well even when \ 
GIT_WORK_TREE is
  set correctly with GIT_DIR if the current directory is outside the working
  tree.
* "git send-email" did not honor the configured hostname when restarting
  the HELO/EHLO exchange after switching TLS on.
* "gitweb" used to produce a non-working link while showing the contents
  of a blob, when JavaScript actions are enabled.

Log message:
Changes 1.7.7:
* The scripting part of the codebase is getting prepared for i18n/l10n.
* Interix, Cygwin and Minix ports got updated.
* Various updates to git-p4 (in contrib/), fast-import, and git-svn.
* Gitweb learned to read from /etc/gitweb-common.conf when it exists,
  before reading from gitweb_config.perl or from /etc/gitweb.conf
* Various codepaths that invoked zlib deflate/inflate assumed that these
  functions can compress or uncompress more than 4GB data in one call on
  platforms with 64-bit long, which has been corrected.
* Git now recognizes loose objects written by other implementations that
  use a non-standard window size for zlib deflation (e.g. Agit running on
  Android with 4kb window). We used to reject anything that was not
  deflated with 32kb window.
* Interaction between the use of pager and coloring of the output has
  been improved, especially when a command that is not built-in was
  involved.
* "git am" learned to pass the "--exclude=<path>" \ 
option through to underlying
  "git apply".
* You can now feed many empty lines before feeding an mbox file to "git \ 
am".
* "git archive" can be told to pass the output to gzip compression and
  produce "archive.tar.gz".
* "git bisect" can be used in a bare repository (provided that the test
  you perform per each iteration does not need a working tree, of course).
* The length of abbreviated object names in "git branch -v" output
  now honors the core.abbrev configuration variable.
* "git check-attr" can take relative paths from the command line.
* "git check-attr" learned an "--all" option to list the \ 
attributes for a
  given path.
* "git checkout" (both the code to update the files upon checking out a
  different branch and the code to checkout a specific set of files) learned
  to stream the data from object store when possible, without having to
  read the entire contents of a file into memory first. An earlier round
  of this code that is not in any released version had a large leak but
  now it has been plugged.
* "git clone" can now take a "--config key=value" option to \ 
set the
  repository configuration options that affect the initial checkout.
* "git commit <paths>..." now lets you feed relative pathspecs that
  refer to outside your current subdirectory.
* "git diff --stat" learned a --stat-count option to limit the output of
  a diffstat report.
* "git diff" learned a "--histogram" option to use a \ 
different diff
  generation machinery stolen from jgit, which might give better performance.
* "git diff" had a weird worst case behaviour that can be triggered
  when comparing files with potentially many places that could match.
* "git fetch", "git push" and friends no longer show connection
  errors for addresses that couldn't be connected to when at least one
  address succeeds (this is arguably a regression but a deliberate one).
* "git grep" learned "--break" and "--heading" \ 
options, to let users mimic
  the output format of "ack".
* "git grep" learned a "-W" option that shows wider context \ 
using the same
  logic used by "git diff" to determine the hunk header.
* Invoking the low-level "git http-fetch" without "-a" \ 
option (which
  git itself never did---normal users should not have to worry about
  this) is now deprecated.
* The "--decorate" option to "git log" and its family learned to
  highlight grafted and replaced commits.
* "git rebase master topci" no longer spews usage hints after giving
  the "fatal: no such branch: topci" error message.
* The recursive merge strategy implementation got a fairly large
  fix for many corner cases that may rarely happen in real world
  projects (it has been verified that none of the 16000+ merges in
  the Linux kernel history back to v2.6.12 is affected with the
  corner case bugs this update fixes).
* "git stash" learned an "--include-untracked option".
* "git submodule update" used to stop at the first error updating a
  submodule; it now goes on to update other submodules that can be
  updated, and reports the ones with errors at the end.
* "git push" can be told with the \ 
"--recurse-submodules=check" option to
  refuse pushing of the supermodule, if any of its submodules'
  commits hasn't been pushed out to their remotes.
* "git upload-pack" and "git receive-pack" learned to \ 
pretend that only a
  subset of the refs exist in a repository. This may help a site to
  put many tiny repositories into one repository (this would not be
  useful for larger repositories as repacking would be problematic).
* "git verify-pack" has been rewritten to use the \ 
"index-pack" machinery
  that is more efficient in reading objects in packfiles.
* test scripts for gitweb tried to run even when CGI-related perl modules
  are not installed; they now exit early when the latter are unavailable.

Log message:
Update to 1.7.6.3 from 1.7.6.1.  Add backup googlecode MASTER_SITE due
to kernel.org issues.

1.7.6.3:

 * "git -c var=value subcmd" misparsed the custom configuration when
   value contained an equal sign.

 * "git fetch" had a major performance regression, wasting many
   needless cycles in a repository where there is no submodules
   present. This was especially bad, when there were many refs.

 * "git reflog $refname" did not default to the "show" \ 
subcommand as
   the documentation advertised the command to do.

 * "git reset" did not leave meaningful log message in the reflog.

 * "git status --ignored" did not show ignored items when there is no
   untracked items.

 * "git tag --contains $commit" was unnecessarily inefficient.

Also contains minor fixes and documentation updates.

1.7.6.2:

Junio C Hamano (3):
      whitespace: have SP on both sides of an assignment "="
      Revert "Merge branch 'cb/maint-quiet-push' into maint"
      Git 1.7.6.2

Pang Yan Han (1):
      update-ref: whitespace fix

Thomas Rast (1):
      Documentation: clarify effects of -- <path> arguments

Log message:
Changes 1.7.6.1:
* Various codepaths that invoked zlib deflate/inflate assumed that these
  functions can compress or uncompress more than 4GB data in one call on
  platforms with 64-bit long, which has been corrected.
* "git unexecutable" reported that "unexecutable" was not \ 
found, even
  though the actual error was that "unexecutable" was found but did
  not have a proper she-bang line to be executed.
* Error exits from $PAGER were silently ignored.
* "git checkout -b <branch>" was confused when attempting to create a
  branch whose name ends with "-g" followed by hexadecimal digits,
  and refused to work.
* "git checkout -b <branch>" sometimes wrote a bogus reflog entry,
  causing later "git checkout -" to fail.
* "git diff --cc" learned to correctly ignore binary files.
* "git diff -c/--cc" mishandled a deletion that resolves a conflict, and
  looked in the working tree instead.
* "git fast-export" forgot to quote pathnames with unsafe characters
  in its output.
* "git fetch" over smart-http transport used to abort when the
  repository was updated between the initial connection and the
  subsequent object transfer.
* "git fetch" did not recurse into submodules in subdirectories.
* "git ls-tree" did not error out when asked to show a corrupt tree.
* "git pull" without any argument left an extra whitespace after the
  command name in its reflog.
* "git push --quiet" was not really quiet.
* "git rebase -i -p" incorrectly dropped commits from side branches.
* "git reset [<commit>] paths..." did not reset the index entry \ 
correctly
  for unmerged paths.
* "git submodule add" did not allow a relative repository path when
  the superproject did not have any default remote url.
* "git submodule foreach" failed to correctly give the standard input to
  the user-supplied command it invoked.
* submodules that the user has never showed interest in by running
  "git submodule init" was incorrectly marked as interesting by "git
  submodule sync".
* "git submodule update --quiet" was not really quiet.
* "git tag -l <glob>..." did not take multiple glob patterns from the
  command line.

Log message:
Revision bump after updating perl5 to 5.14.1.

Log message:
Changes 1.7.6:
* Various git-svn updates.
* Updates the way content tags are handled in gitweb.  Also adds
  a UI to choose common timezone for displaying the dates.
* Similar to branch names, tagnames that begin with "-" are now
  disallowed.
* Clean-up of the C part of i18n (but not l10n---please wait)
  continues.
* The scripting part of the codebase is getting prepared for i18n/l10n.
* Pushing and pulling from a repository with large number of refs that
  point to identical commits are optimized by not listing the same commit
  during the common ancestor negotiation exchange with the other side.
* Adding a file larger than core.bigfilethreshold (defaults to 1/2 Gig)
  using "git add" will send the contents straight to a packfile without
  having to hold it and its compressed representation both at the same
  time in memory.
* Processes spawned by "[alias] <name> = !process" in the \ 
configuration
  can inspect GIT_PREFIX environment variable to learn where in the
  working tree the original command was invoked.
* A magic pathspec ":/" tells a command that limits its operation to
  the current directory when ran from a subdirectory to work on the
  entire working tree. In general, ":/path/to/file" would be relative
  to the root of the working tree hierarchy.
  After "git reset --hard; edit Makefile; cd t/", "git add \ 
-u" would
  be a no-op, but "git add -u :/" would add the updated contents of
  the Makefile at the top level. If you want to name a path in the
  current subdirectory whose unusual name begins with ":/", you can
  name it by "./:/that/path" or by "\:/that/path".
* "git blame" learned "--abbrev[=<n>]" option to \ 
control the minimum
  number of hexdigits shown for commit object names.
* "git blame" learned "--line-porcelain" that is less \ 
efficient but is
  easier to parse.
* Aborting "git commit --interactive" discards updates to the index
  made during the interactive session.
* More...

Log message:
Changes 1.7.5.4:
* The single-key mode of "git add -p" was easily fooled into thinking
  that it was told to add everthing ('a') when up-arrow was pressed by
  mistake.
* Setting a git command that uses custom configuration via "-c var=val"
  as an alias caused a crash due to a realloc(3) failure.
* "git diff -C -C" used to disable the rename detection entirely when
  there are too many copy candidate paths in the tree; now it falls
  back to "-C" when doing so would keep the copy candidate paths
  under the rename detection limit.
* "git rerere" did not diagnose a corrupt MERGE_RR file in some cases.

Log message:
Fix typo. Reported on IRC.

Log message:
Changes 1.7.5.2:
* "git add -p" did not work correctly when a hunk is split and then
  one of them was given to the editor.
* "git add -u" did not resolve a conflict where our history deleted and
  their history modified the same file, and the working tree resolved to
  keep a file.
* "git cvsimport" did not know that CVSNT stores its password file in a
  location different from the traditional CVS.
* "git diff-files" did not show the mode information from the working
  tree side of an unmerged path correctly.
* "git diff -M --cached" used to use unmerged path as a possible rename
  source candidate, which made no sense.
* The option name parser in "git fast-import" used prefix matches for
  some options where it shouldn't, and accepted non-existent options,
  e.g. "--relative-marksmith" or "--forceps".
* "git format-patch" did not quote RFC822 special characters in the
  email address (e.g From: Junio C. Hamano <jch@example.com>, not
  From: "Junio C. Hamano" <jch@example.com>).
* "git format-patch" when run with "--quiet" option used to \ 
produce a
  nonsense result that consists of alternating empty output.
* In "git merge", per-branch branch.<name>.mergeoptions configuration
  variables did not override the fallback default merge.<option>
  configuration variables such as merge.ff, merge.log, etc.
* "git merge-one-file" did not honor GIT_WORK_TREE settings when
  handling a "both sides added, differently" conflict.
* "git mergetool" did not handle conflicted submoudules gracefully.
* "git-p4" (in contrib) used a wrong base image while merge a file that
  was added on both branches differently.
* "git rebase -i -p" failed to preserve the history when there is a
  redundant merge created with the --no-ff option.