The Git team released version 184.108.40.206 and I made this version available in my Ubuntu repository. Besides the usual suspects, Ubuntu 10.04, 10.10, 11.04 and 11.10, it’s now also available for the upcoming Ubuntu 12.04 (Precise) release.
The version currently shipping with Ubuntu 12.04 (Precise) is git v220.127.116.11.
To use my repository follow the instructions on the page Git Packages for Ubuntu.
Overview of changes since v18.104.22.168
Git v22.214.171.124 Release Notes
Fixes since v126.96.36.199 -------------------- * 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 " 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.
Git v188.8.131.52 Release Notes
Fixes since v184.108.40.206 -------------------- * "git p4" (in contrib/) submit the changes to a wrong place when the "--use-client-spec" option is set. * The config.mak.autogen generated by optional autoconf support tried to link the binary with -lintl even when libintl.h is missing from the system. * When the filter driver exits before reading the content before the main git process writes the contents to be filtered to the pipe to it, the latter could be killed with SIGPIPE instead of ignoring such an event as an error. * "git add --refresh
" used to warn about unmerged paths outside the given pathspec. * The bulk check-in codepath in "git add" streamed contents that needs smudge/clean filters without running them, instead of punting and delegating to the codepath to run filters after slurping everything to core. * "git branch --with $that" assumed incorrectly that the user will never ask the question with nonsense value in $that. * "git bundle create" produced a corrupt bundle file upon seeing commits with excessively long subject line. * When a remote helper exits before reading the blank line from the main git process to signal the end of commands, the latter could be killed with SIGPIPE. Instead we should ignore such event as a non-error. * The commit log template given with "git merge --edit" did not have a short instructive text like what "git commit" gives. * "git rev-list --verify-objects -q" omitted the extra verification it needs to do over "git rev-list --objects -q" by mistake. * "gitweb" used to drop warnings in the log file when "heads" view is accessed in a repository whose HEAD does not point at a valid branch. * An invalid regular expression pattern given by an end user made "gitweb" to return garbled response. Also contains minor fixes and documentation updates.
Git v220.127.116.11 Release Notes
Fixes since v18.104.22.168 -------------------- * The code to synthesize the fake ancestor tree used by 3-way merge fallback in "git am" was not prepared to read a patch created with a non-standard -p
value. * "git bundle" did not record boundary commits correctly when there are many of them. * "git diff-index" and its friends at the plumbing level showed the "diff --git" header and nothing else for a path whose cached stat info is dirty without actual difference when asked to produce a patch. This was a longstanding bug that we could have fixed long time ago. * "gitweb" did use quotemeta() to prepare search string when asked to do a fixed-string project search, but did not use it by mistake and used the user-supplied string instead. Also contains minor fixes and documentation updates.