1 Git v1.7.10 Release Notes
2 =========================
7 UI, Workflows & Features
9 * Improved handling of views, labels and branches in git-p4 (in contrib).
11 * "git-p4" (in contrib) suffered from unnecessary merge conflicts when
12 p4 expanded the embedded $RCS$-like keywords; it can be now told to
15 * Some "git-svn" updates.
17 * "vcs-svn"/"svn-fe" learned to read dumps with svn-deltas and
18 support incremental imports.
20 * The configuration mechanism learned an "include" facility; an
21 assignment to the include.path pseudo-variable causes the named
22 file to be included in-place when Git looks up configuration
25 * A content filter (clean/smudge) used to be just a way to make the
26 recorded contents "more useful", and allowed to fail; a filter can
27 new optionally be marked as "required".
29 * "git am" learned to pass "-b" option to underlying "git mailinfo", so
30 that bracketed string other than "PATCH" at the beginning can be kept.
32 * "git clone" learned "--single-branch" option to limit cloning to a
33 single branch (surprise!).
35 * "git clone" learned to detach the HEAD in the resulting repository
36 when the source repository's HEAD does not point to a branch.
38 * When showing a patch while ignoring whitespace changes, the context
39 lines are taken from the postimage, in order to make it easier to
42 * "diff-highlight" filter (in contrib/) was updated to produce more
43 aesthetically pleasing output.
45 * "git merge" in an interactive session learned to spawn the editor
46 by default to let the user edit the auto-generated merge message,
47 to encourage people to explain their merges better. Legacy scripts
48 can export GIT_MERGE_AUTOEDIT=no to retain the historical behavior.
49 Both "git merge" and "git pull" can be given --no-edit from the
50 command line to accept the auto-generated merge message.
52 * "git push" learned the "--prune" option, similar to "git fetch".
54 * "git tag --list" can be given "--points-at <object>" to limit its
55 output to those that point at the given object.
57 * "gitweb" allows intermediate entries in the directory hierarchy
58 that leads to a projects to be clicked, which in turn shows the
59 list of projects inside that directory.
61 * "gitweb" learned to read various pieces of information for the
62 repositories lazily, instead of reading everything that could be
63 needed (including the ones that are not necessary for a specific
68 * During "git upload-pack" in response to "git fetch", unnecessary calls
69 to parse_object() have been eliminated, to help performance in
70 repositories with excessive number of refs.
72 Internal Implementation (please report possible regressions)
74 * Recursive call chains in "git index-pack" to deal with long delta
75 chains have been flattened, to reduce the stack footprint.
77 * Use of add_extra_ref() API is now gone, to make it possible to
78 cleanly restructure the overall refs API.
80 * The command line parser of "git pack-objects" now uses parse-options
83 * The test suite supports the new "test_pause" helper function.
85 * Parallel to the test suite, there is a beginning of performance
86 benchmarking framework.
88 * t/Makefile is adjusted to prevent newer versions of GNU make from
89 running tests in seemingly random order.
91 Also contains minor documentation updates and code clean-ups.
97 Unless otherwise noted, all the fixes since v1.7.9 in the maintenance
98 releases are contained in this release (see release notes to them for
101 * The bulk check-in codepath streamed contents that needs
102 smudge/clean filters without running them, instead of punting and
103 delegating to the codepath to run filters after slurping everything
105 (merge 4f22b10 jk/maint-avoid-streaming-filtered-contents later to maint).
107 * When the filter driver exits before reading the content before the
108 main git process writes the contents to be filtered to the pipe to
109 it, the latter could be killed with SIGPIPE instead of ignoring
110 such an event as an error.
111 (merge 6424c2a jb/filter-ignore-sigpipe later to maint).
113 * When a remote helper exits before reading the blank line from the
114 main git process to signal the end of commands, the latter could be
115 killed with SIGPIPE. Instead we should ignore such event as a
117 (merge c34fe63 sp/smart-http-failure-to-push later to maint).
119 * "git bundle create" produced a corrupt bundle file upon seeing
120 commits with excessively long subject line.
121 (merge 8a557bb tr/maint-bundle-long-subject later to maint).
123 * "gitweb" used to drop warnings in the log file when "heads" view is
124 accessed in a repository whose HEAD does not point at a valid
129 O=v1.7.9.2-322-g472fdee
130 echo O=$(git describe)
131 git log --first-parent --oneline ^maint $O..
133 git shortlog --no-merges ^maint $O..