A release candidate Git 1.7.10-rc0 is now available for testing at
the usual places.
The release tarballs are found at:
and their SHA-1 checksums are:
96d1d25fd4f681246009b24fcaa4e41d88223f5b git-1.7.10.rc0.tar.gz a8c76f12980a287e0f6a0f285768ab492caaed98 git-htmldocs-1.7.10.rc0.tar.gz 8f5f8aa4f692eb3d6e3549f6eb0fb0b5419c2f57 git-manpages-1.7.10.rc0.tar.gz
Also the following public repositories all have a copy of the v1.7.10.rc0
tag and the master branch that the tag points at:
url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git
The other day, soon after announcement of the 220.127.116.11 maintenance
release, there was a report that some tests did not pass on one
platform. Even though it is better than not seeing one, such a late
report saddens us, especially because the exact test breakage has
been in the master and next branches for quite some time for people
to catch before it goes to any released versions.
Please test this and later pre-releases to make sure no such late
report has to come for the upcoming 1.7.10 final.
Git v1.7.10 Release Notes (draft)
* From this release on, the "git merge" command in an interactive session will start an editor when it automatically resolves the merge for the user to explain the resulting commit, just like the "git commit" command does when it wasn't given a commit message. + If you have a script that runs "git merge" and keeps its standard input and output attached to the user's terminal, and if you do not want the user to explain the resulting merge commits, you can export GIT_MERGE_AUTOEDIT environment variable set to "no", like this: #!/bin/sh GIT_MERGE_AUTOEDIT=no export GIT_MERGE_AUTOEDIT to disable this behaviour (if you want your users to explain their merge commits, you do not have to do anything). Alternatively, you can give the "--no-edit" option to individual invocations of the "git merge" command if you know everybody who uses your script has Git v1.7.8 or newer. Updates since v1.7.9 -------------------- UI, Workflows & Features * Teams for localizing the messages from the Porcelain layer of commands are starting to form, thanks to Jiang Xin who volunteered to be the localization coordinator. An initial set of translated messages for simplified chinese is available. * The configuration mechanism learned an "include" facility; an assignment to the include.path pseudo-variable causes the named file to be included in-place when Git looks up configuration variables. * A content filter (clean/smudge) used to be just a way to make the recorded contents "more useful", and allowed to fail; a filter can new optionally be marked as "required". * Options whose names begin with "--no-" (e.g. the "--no-verify" option of the "git commit" command) can be negated by omitting "no-" from its name, e.g. "git commit --verify". * "git am" learned to pass "-b" option to underlying "git mailinfo", so that bracketed string other than "PATCH" at the beginning can be kept. * "git clone" learned "--single-branch" option to limit cloning to a single branch (surprise!). * "git clone" learned to detach the HEAD in the resulting repository when the source repository's HEAD does not point to a branch. * When showing a patch while ignoring whitespace changes, the context lines are taken from the postimage, in order to make it easier to view the output. * "git diff --stat" learned to adjust the width of the output on wider terminals, and give more columns to pathnames as needed. * "diff-highlight" filter (in contrib/) was updated to produce more aesthetically pleasing output. * "fsck" learned "--no-dangling" option to omit dangling object information. * "git log -G" learned to pay attention to the "-i" option and can find patch hunks that introduce or remove a string that matches the given pattern ignoring the case. * "git merge" in an interactive session learned to spawn the editor by default to let the user edit the auto-generated merge message, to encourage people to explain their merges better. Legacy scripts can export GIT_MERGE_AUTOEDIT=no to retain the historical behavior. Both "git merge" and "git pull" can be given --no-edit from the command line to accept the auto-generated merge message. * The advise message given when the user didn't give enough clue on what to merge to "git pull" and "git merge" has been updated to be more concise and easier to understand. * "git push" learned the "--prune" option, similar to "git fetch". * "git symbolic-ref" learned the "--short" option to abbreviate the refname it shows unambiguously. * "git tag --list" can be given "--points-at <object>" to limit its output to those that point at the given object. * "gitweb" allows intermediate entries in the directory hierarchy that leads to a projects to be clicked, which in turn shows the list of projects inside that directory. * "gitweb" learned to read various pieces of information for the repositories lazily, instead of reading everything that could be needed (including the ones that are not necessary for a specific task). * Project search in "gitweb" shows the substring that matched in the project name and description highlighted. Foreign Interface * Improved handling of views, labels and branches in "git-p4" (in contrib). * "git-p4" (in contrib) suffered from unnecessary merge conflicts when p4 expanded the embedded $RCS$-like keywords; it can be now told to unexpand them. * Some "git-svn" updates. * "vcs-svn"/"svn-fe" learned to read dumps with svn-deltas and support incremental imports. * "git difftool/mergetool" learned to drive DeltaWalker. Performance * Unnecessary calls to parse_object() "git upload-pack" makes in response to "git fetch", have been eliminated, to help performance in repositories with excessive number of refs. Internal Implementation (please report possible regressions) * Recursive call chains in "git index-pack" to deal with long delta chains have been flattened, to reduce the stack footprint. * Use of add_extra_ref() API is now gone, to make it possible to cleanly restructure the overall refs API. * The command line parser of "git pack-objects" now uses parse-options API. * The test suite supports the new "test_pause" helper function. * Parallel to the test suite, there is a beginning of performance benchmarking framework. * t/Makefile is adjusted to prevent newer versions of GNU make from running tests in seemingly random order. * The code to check if a path points at a file beyond a symbolic link has been restructured to be thread-safe. Also contains minor documentation updates and code clean-ups. Fixes since v1.7.9 ------------------ Unless otherwise noted, all the fixes since v1.7.9 in the maintenance releases are contained in this release (see release notes to them for details). * "git bundle" did not record boundary commits correctly when there are many of them. (merge efe4be1 tr/maint-bundle-boundary later to maint). * "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. (merge b3f01ff jc/maint-diff-patch-header later to maint). * 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<num> value. (merge a61ba26 jc/am-3-nonstandard-popt later to maint). * "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.
Junio C Hamano wrote on 07 Mar 2012