Log message:
Changes 1.7.5.1:
* When an object "$tree:$path" does not exist, if $path does exist in the
  subtree of $tree that corresponds to the subdirectory the user is in,
  git now suggests using "$tree:./$path" in addition to the advice to use
  the full path from the root of the working tree.
* The "--date=relative" output format used to say "X years, 12 \ 
months"
  when it should have said "X+1 years".
* The smart-HTTP transfer was broken in 1.7.5 when the client needs
  to issue a small POST (which uses content-length) and then a large
  POST (which uses chunked) back to back.
* "git clean" used to fail on an empty directory that is not readable,
  even though rmdir(2) could remove such a directory.  Now we attempt it
  as the last resort.
* The "--dirstat" option of "diff" family of commands used \ 
to totally
  ignore a change that only rearranged lines within a file.  Such a
  change now counts as at least a minimum but non zero change.
* The "--dirstat" option of "diff" family of commands used \ 
to use the
  pathname in the original, instead of the pathname in the result,
  when renames are involved.
* "git pack-object" did not take core.bigfilethreashold into account
  (unlike fast-import); now it does.
* "git reflog" ignored options like "--format=.." on the \ 
command line.
* "git stash apply" used to refuse to work if there was any change in
  the working tree, even when the change did not overlap with the change
  the stash recorded.
* "git stash apply @{99999}" was not diagnosed as an error, even when you
  did not have that many stash entries.
* An error message from "git send-email" to diagnose a broken SMTP
  connection configuration lacked a space between \ 
"hello=<smtp-domain>"
  and "port=<smtp-server-port>".

Log message:
Fix a PLIST entry condition for -scmgit-gui option, and sort.

Log message:
Changes 1.7.5:
* Various MinGW portability fixes.
* Various git-p4 enhancements (in contrib).
* Various vcs-svn, git-svn and gitk enhancements and fixes.
* Various git-gui updates (0.14.0).
* Update to more modern HP-UX port.
* The codebase is getting prepared for i18n/l10n; no translated
  strings nor translation mechanism in the code yet, but the strings
  are being marked for l10n.
* The bash completion script can now complete symmetric difference
  for "git diff" command, e.g. "git diff ...bra<TAB>".
* The default minimum length of abbreviated and unique object names
  can now be configured by setting the core.abbrev configuration
  variable.
* "git apply -v" reports offset lines when the patch does not apply at
  the exact location recorded in the diff output.
* "git config" used to be also known as "git repo-config", \ 
but the old
  name is now officially deprecated.
* "git checkout --detach <commit>" is a more user friendly \ 
synonym for
  "git checkout <commit>^0".
* "git checkout" performed on detached HEAD gives a warning and
  advice when the commit being left behind will become unreachable from
  any branch or tag.
* "git cherry-pick" and "git revert" can be told to use a \ 
custom merge
  strategy, similar to "git rebase".
* "git cherry-pick" remembers which commit failed to apply when it is
  stopped by conflicts, making it unnecessary to use "commit -c $commit"
  to conclude it.
* "git cvsimport" bails out immediately when the cvs server cannot be
  reached, without spewing unnecessary error messages that complain about
  the server response it never got.
* "git fetch" vs "git upload-pack" transfer learned 'no-done'
  protocol extension to save one round-trip after the content
  negotiation is done. This saves one HTTP RPC, reducing the overall
  latency for a trivial fetch.
* "git fetch" can be told to recursively fetch submodules on-demand.
* "git grep -f <filename>" learned to treat "-" as \ 
"read from the
  standard input stream".
* "git grep --no-index" did not honor pathspecs correctly, returning
  paths outside the specified area.
* "git init" learned the --separate-git-dir option to allow the git
  directory for a new repository created elsewhere and linked via the
  gitdir mechanism. This is primarily to help submodule support later
  to switch between a branch of superproject that has the submodule
  and another that does not.
* "git log" type commands now understand globbing pathspecs.  You
  can say "git log -- '*.txt'" for example.
* "git log" family of commands learned --cherry and --cherry-mark
  options that can be used to view two diverged branches while omitting
  or highlighting equivalent changes that appear on both sides of a
  symmetric difference (e.g. "log --cherry A...B").
* A lazy "git merge" that didn't say what to merge used to be an error.
  When run on a branch that has an upstream defined, however, the command
  now merges from the configured upstream.
* "git mergetool" learned how to drive "beyond compare 3" as \ 
well.
* "git rerere forget" without pathspec used to forget all the saved
  conflicts that relate to the current merge; it now requires you to
  give it pathspecs.
* "git rev-list --objects $revs -- $pathspec" now limits the objects listed
  in its output properly with the pathspec, in preparation for narrow
  clones.
* "git push" with no parameters gives better advice messages when
  "tracking" is used as the push.default semantics or there is no remote
  configured yet.
* A possible value to the "push.default" configuration variable,
  'tracking', gained a synonym that more naturally describes what it
  does, 'upstream'.
* "git rerere" learned a new subcommand "remaining" that is \ 
similar to
  "status" and lists the paths that had conflicts which are known to
  rerere, but excludes the paths that have already been marked as
  resolved in the index from its output.  "git mergetool" has been
  updated to use this facility.

Log message:
recursive bump from gettext-lib shlib bump.

Log message:
-Python is optional, keep this in options.mk
-the files where the interpreter check fires are not executable,
 so just CHECK_INTERPRETER_SKIP them

Log message:
Use python correctly.

Log message:
Changes 1.7.4.4:
* Compilation of sha1_file.c on BSD platforms were broken due to our
  recent use of getrlimit() without including <sys/resource.h>.
* "git config" did not diagnose incorrect configuration variable names.
* "git format-patch" did not wrap a long subject line that resulted from
  rfc2047 encoding.
* "git instaweb" should work better again with plackup.
* "git log --max-count=4 -Sfoobar" now shows 4 commits that changes the
  number of occurrences of string "foobar"; it used to scan only for 4
  commits and then emitted only matching ones.
* "git log --first-parent --boundary $c^..$c" segfaulted on a merge.
* "git pull" into an empty branch should have behaved as if
  fast-forwarding from emptiness to the version being pulled, with
  the usual protection against overwriting untracked files.
* "git submodule" that is run while a merge in the superproject is in
  conflicted state tried to process each conflicted submodule up to
  three times.
* "git status" spent all the effort to notice racily-clean index entries
  but didn't update the index file to help later operations go faster in
  some cases.

Log message:
Changes 1.7.4.3:
* "git apply" used to confuse lines updated by previous hunks as lines
  that existed before when applying a hunk, contributing misapplication
  of patches with offsets.
* "git branch --track" (and "git checkout --track --branch") \ 
used to
  allow setting up a random non-branch that does not make sense to follow
  as the "upstream".  The command correctly diagnoses it as an error.
* "git checkout $other_branch" silently removed untracked symbolic links
  in the working tree that are in the way in order to check out paths
  under it from the named branch.
* "git cvsimport" did not bail out immediately when the cvs server cannot
  be reached, spewing unnecessary error messages that complain about the
  server response that it never got.
* "git diff --quiet" did not work very well with the \ 
"--diff-filter" option.
* "git grep -n" lacked a long-hand synonym --line-number.
* "git stash apply" reported the result of its operation by running
  "git status" from the top-level of the working tree; it should (and
  now does) run it from the user's working directory.

Log message:
Changes 1.7.4.1:
* On Windows platform, the codepath to spawn a new child process forgot
  to first flush the output buffer.
* "git bundle" did not use OFS_DELTA encoding, making its output a few
  per-cent larger than necessarily.
* The option to tell "git clone" to recurse into the submodules was
  misspelled with an underscore "--recurse_submodules".
* "git diff --cached HEAD" before the first commit does what an end user
  would expect (namely, show what would be committed without further "git
  add").
* "git fast-import" didn't accept the command to ask for \ 
"notes" feature
  to be present in its input stream, even though it was capable of the
  feature.
* "git fsck" gave up scanning loose object files in directories with
  garbage files.

Log message:
Changes 1.7.3.5:
* The xfuncname pattern used by "git diff" and "git grep" to \ 
show the
  last notable line in context were broken for python and ruby for a long
  time.
* "git merge" into an unborn branch removed an untracked file \ 
"foo" from
  the working tree when merged branch had "foo" (this fix was already in
  1.7.3.3 but was omitted from the release notes by mistake).
* "git status -s" did not quote unprintable characters in paths as
  documented.
* "git am --abort" used to always reset to the commit at the beginning of
  the last "am" invocation that has stopped, losing any unrelated commits
  that may have been made since then.  Now it refrains from doing so and
  instead issues a warning.
* "git blame" incorrectly reused bogusly cached result of textconv
  filter for files from the working tree.
* "git commit" used to abort after the user edited the log message
  when the committer information was not correctly set up.  It now
  aborts before starting the editor.
* "git commit --date=invalid" used to silently ignore the incorrectly
  specified date; it is now diagnosed as an error.
* "git rebase --skip" to skip the last commit in a series used to fail
  to run post-rewrite hook and to copy notes from old commits that have
  successfully been rebased so far.  Now it do (backmerge ef88ad2).
* "gitweb" tried to show a wrong feed logo when none was specified.