Log message:
Add "used by" comments

Log message:
Update to 1.7.9.2.

Fixes since v1.7.9.1
--------------------

 * Bash completion script (in contrib/) did not like a pattern that
   begins with a dash to be passed to __git_ps1 helper function.

 * Adaptation of the bash completion script (in contrib/) for zsh
   incorrectly listed all subcommands when "git \ 
<TAB><TAB>" was given
   to ask for list of porcelain subcommands.

 * The build procedure for profile-directed optimized binary was not
   working very well.

 * Some systems need to explicitly link -lcharset to get locale_charset().

 * t5541 ignored user-supplied port number used for HTTP server testing.

 * The error message emitted when we see an empty loose object was
   not phrased correctly.

 * The code to ask for password did not fall back to the terminal
   input when GIT_ASKPASS is set but does not work (e.g. lack of X
   with GUI askpass helper).

 * We failed to give the true terminal width to any subcommand when
   they are invoked with the pager, i.e. "git -p cmd".

 * map_user() was not rewriting its output correctly, which resulted
   in the user visible symptom that "git blame -e" sometimes showed
   excess '>' at the end of email addresses.

 * "git checkout -b" did not allow switching out of an unborn branch.

 * When you have both .../foo and .../foo.git, "git clone .../foo" did not
   favor the former but the latter.

 * "git commit" refused to create a commit when entries added with
   "add -N" remained in the index, without telling Git what their content
   in the next commit should be. We should have created the commit without
   these paths.

 * "git diff --stat" said "files", "insertions", \ 
and "deletions" even
   when it is showing one "file", one "insertion" or one \ 
"deletion".

 * The output from "git diff --stat" for two paths that have the same
   amount of changes showed graph bars of different length due to the
   way we handled rounding errors.

 * "git grep" did not pay attention to -diff (hence -binary) attribute.

 * The transport programs (fetch, push, clone)ignored --no-progress
   and showed progress when sending their output to a terminal.

 * Sometimes error status detected by a check in an earlier phase of
   "git receive-pack" (the other end of "git push") was lost \ 
by later
   checks, resulting in false indication of success.

 * "git rev-list --verify" sometimes skipped verification depending on
   the phase of the moon, which dates back to 1.7.8.x series.

 * Search box in "gitweb" did not accept non-ASCII characters correctly.

 * Search interface of "gitweb" did not show multiple matches in the \ 
same file
   correctly.

Also contains minor fixes and documentation updates.

Log message:
Update to 1.7.9.1.

(This is a bugfix release relative to 1.7.9.)

Log message:
Changes 1.7.9:
* gitk updates accumulated since early 2011.
* git-gui updated to 0.16.0.
* git-p4 (in contrib/) updates.
* Git uses gettext to translate its most common interface messages
  into the user's language if translations are available and the
  locale is appropriately set. Distributors can drop new PO files
  in po/ to add new translations.
* The code to handle username/password for HTTP transactions used in
  "git push" & "git fetch" learned to talk \ 
"credential API" to
  external programs to cache or store them, to allow integration with
  platform native keychain mechanisms.
* The input prompts in the terminal use our own getpass() replacement
  when possible. HTTP transactions used to ask for the username without
  echoing back what was typed, but with this change you will see it as
  you type.
* The internals of "revert/cherry-pick" have been tweaked to prepare
  building more generic "sequencer" on top of the implementation that
  drives them.
* "git rev-parse FETCH_HEAD" after "git fetch" without specifying
  what to fetch from the command line will now show the commit that
  would be merged if the command were "git pull".
* "git add" learned to stream large files directly into a packfile
  instead of writing them into individual loose object files.
* "git checkout -B <current branch> <elsewhere>" is a more \ 
intuitive
  way to spell "git reset --keep <elsewhere>".
* "git checkout" and "git merge" learned \ 
"--no-overwrite-ignore" option
  to tell Git that untracked and ignored files are not expendable.
* "git commit --amend" learned "--no-edit" option to say that the
  user is amending the tree being recorded, without updating the
  commit log message.
* "git commit" and "git reset" re-learned the optimization \ 
to prime
  the cache-tree information in the index, which makes it faster to
  write a tree object out after the index entries are updated.
* "git commit" detects and rejects an attempt to stuff NUL byte in
  the commit log message.
* "git commit" learned "-S" to GPG-sign the commit; this can \ 
be shown
  with the "--show-signature" option to "git log".
* fsck and prune are relatively lengthy operations that still go
  silent while making the end-user wait. They learned to give progress
  output like other slow operations.
* The set of built-in function-header patterns for various languages
  knows MATLAB.
* "git log --format='<format>'" learned new %g[nNeE] specifiers to
  show information from the reflog entries when walking the reflog
  (i.e. with "-g").
* "git pull" can be used to fetch and merge an annotated/signed tag,
  instead of the tip of a topic branch. The GPG signature from the
  signed tag is recorded in the resulting merge commit for later
  auditing.
* "git log" learned "--show-signature" option to show the \ 
signed tag
  that was merged that is embedded in the merge commit. It also can
  show the signature made on the commit with "git commit -S".
* "git branch --edit-description" can be used to add descriptive text
  to explain what a topic branch is about.
* "git fmt-merge-msg" learned to take the branch description into
  account when preparing a merge summary that "git merge" records
  when merging a local branch.
* "git request-pull" has been updated to convey more information
  useful for integrators to decide if a topic is worth merging and
  what is pulled is indeed what the requestor asked to pull,
  including:
  - the tip of the branch being requested to be merged;
  - the branch description describing what the topic is about;
  - the contents of the annotated tag, when requesting to pull a tag.
* "git pull" learned to notice 'pull.rebase' configuration variable,
  which serves as a global fallback for setting 'branch.<name>.rebase'
  configuration variable per branch.
* "git tag" learned "--cleanup" option to control how the \ 
whitespaces
  and empty lines in tag message are cleaned up.
* "gitweb" learned to show side-by-side diff.

Log message:
Replace obsolete configure flag with override.

Log message:
Changes 1.7.8.4:
* The code to look up attributes for paths reused entries from a wrong
  directory when two paths in question are in adjacent directories and
  the name of the one directory is a prefix of the other.
* A wildcard that matches deeper hierarchy given to the "diff-index" \ 
command,
  e.g. "git diff-index HEAD -- '*.txt'", incorrectly reported additions of
  matching files even when there is no change.
* When producing a "thin pack" (primarily used in bundles and smart
  HTTP transfers) out of a fully packed repository, we unnecessarily
  avoided sending recent objects as a delta against objects we know
  the other side has.
* "git send-email" did not properly treat sendemail.multiedit as a
  boolean (e.g. setting it to "false" did not turn it off).
* Also contains minor fixes and documentation updates.

Log message:
Update to 1.7.7.6 from 1.7.7.2.

Fixes since v1.7.7.2
--------------------

 * Adjust the "quick-install-doc" procedures as preformatted
   html/manpage are no longer in the source repository.

 * The logic to optimize the locality of the data in a pack introduced in
   1.7.7 was grossly inefficient.

 * The logic to filter out forked projects in the project list in
   "gitweb" was broken for some time.

 * "git branch -m/-M" advertised to update RENAME_REF ref in the
   commit log message that introduced the feature but not anywhere in
   the documentation, and never did update such a ref anyway. This
   undocumented misfeature that did not exist has been excised.

Fixes since v1.7.7.3
--------------------

 * A few header dependencies were missing from the Makefile.

 * Some newer parts of the code used C99 __VA_ARGS__ while we still
   try to cater to older compilers.

 * "git name-rev --all" tried to name all _objects_, naturally failing to
   describe many blobs and trees, instead of showing only commits as
   advertised in its documentation.

Fixes since v1.7.7.4
--------------------

 * After fetching from a remote that has very long refname, the reporting
   output could have corrupted by overrunning a static buffer.

 * "git checkout" and "git merge" treated in-tree .gitignore \ 
and exclude
   file in $GIT_DIR/info/ directory inconsistently when deciding which
   untracked files are ignored and expendable.

Fixes since v1.7.7.5
--------------------

 * The code to look up attributes for paths reused entries from a wrong
   directory when two paths in question are in adjacent directories and
   the name of the one directory is a prefix of the other.

 * A wildcard that matches deeper hierarchy given to the "diff-index" \ 
command,
   e.g. "git diff-index HEAD -- '*.txt'", incorrectly reported additions of
   matching files even when there is no change.

 * When producing a "thin pack" (primarily used in bundles and smart
   HTTP transfers) out of a fully packed repository, we unnecessarily
   avoided sending recent objects as a delta against objects we know
   the other side has.

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.