1 Git v1.7.10 Release Notes
2 =========================
7 UI, Workflows & Features
9 * Teams for localizing the messages from the Porcelain layer of
10 commands are starting to form, thanks to Jiang Xin who volunteered
11 to be the localization coordinator. An initial set of translated
12 messages for simplified chinese is available.
14 * The configuration mechanism learned an "include" facility; an
15 assignment to the include.path pseudo-variable causes the named
16 file to be included in-place when Git looks up configuration
19 * A content filter (clean/smudge) used to be just a way to make the
20 recorded contents "more useful", and allowed to fail; a filter can
21 new optionally be marked as "required".
23 * Options whose names begin with "--no-" (e.g. the "--no-verify"
24 option of the "git commit" command) can be negated by omitting
25 "no-" from its name, e.g. "git commit --verify".
27 * "git am" learned to pass "-b" option to underlying "git mailinfo", so
28 that bracketed string other than "PATCH" at the beginning can be kept.
30 * "git clone" learned "--single-branch" option to limit cloning to a
31 single branch (surprise!).
33 * "git clone" learned to detach the HEAD in the resulting repository
34 when the source repository's HEAD does not point to a branch.
36 * When showing a patch while ignoring whitespace changes, the context
37 lines are taken from the postimage, in order to make it easier to
40 * "diff-highlight" filter (in contrib/) was updated to produce more
41 aesthetically pleasing output.
43 * "fsck" learned "--no-dangling" option to omit dangling object
46 * "git merge" in an interactive session learned to spawn the editor
47 by default to let the user edit the auto-generated merge message,
48 to encourage people to explain their merges better. Legacy scripts
49 can export GIT_MERGE_AUTOEDIT=no to retain the historical behavior.
50 Both "git merge" and "git pull" can be given --no-edit from the
51 command line to accept the auto-generated merge message.
53 * "git push" learned the "--prune" option, similar to "git fetch".
55 * "git symbolic-ref" learned the "--short" option to abbreviate the
56 refname it shows unambiguously.
58 * "git tag --list" can be given "--points-at <object>" to limit its
59 output to those that point at the given object.
61 * "gitweb" allows intermediate entries in the directory hierarchy
62 that leads to a projects to be clicked, which in turn shows the
63 list of projects inside that directory.
65 * "gitweb" learned to read various pieces of information for the
66 repositories lazily, instead of reading everything that could be
67 needed (including the ones that are not necessary for a specific
70 * Project search in "gitweb" shows the substring that matched in the
71 project name and description highlighted.
75 * Improved handling of views, labels and branches in git-p4 (in contrib).
77 * "git-p4" (in contrib) suffered from unnecessary merge conflicts when
78 p4 expanded the embedded $RCS$-like keywords; it can be now told to
81 * Some "git-svn" updates.
83 * "vcs-svn"/"svn-fe" learned to read dumps with svn-deltas and
84 support incremental imports.
88 * During "git upload-pack" in response to "git fetch", unnecessary calls
89 to parse_object() have been eliminated, to help performance in
90 repositories with excessive number of refs.
92 Internal Implementation (please report possible regressions)
94 * Recursive call chains in "git index-pack" to deal with long delta
95 chains have been flattened, to reduce the stack footprint.
97 * Use of add_extra_ref() API is now gone, to make it possible to
98 cleanly restructure the overall refs API.
100 * The command line parser of "git pack-objects" now uses parse-options
103 * The test suite supports the new "test_pause" helper function.
105 * Parallel to the test suite, there is a beginning of performance
106 benchmarking framework.
108 * t/Makefile is adjusted to prevent newer versions of GNU make from
109 running tests in seemingly random order.
111 Also contains minor documentation updates and code clean-ups.
117 Unless otherwise noted, all the fixes since v1.7.9 in the maintenance
118 releases are contained in this release (see release notes to them for
121 * The code to synthesize the fake ancestor tree used by 3-way merge
122 fallback in "git am" was not prepared to read a patch created with
123 a non-standard -p<num> value.
124 (merge a61ba26 jc/am-3-nonstandard-popt later to maint).
126 * "gitweb" used to drop warnings in the log file when "heads" view is
127 accessed in a repository whose HEAD does not point at a valid
132 O=v1.7.9.2-383-gb8b5290
133 echo O=$(git describe)
134 git log --first-parent --oneline ^maint $O..
136 git shortlog --no-merges ^maint $O..
projects / thirdparty / git.git / blob