1Git v1.7.10 Release Notes 2========================= 3 4Updates since v1.7.9 5-------------------- 6 7UI, Workflows & Features 8 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. 13 14 * Improved handling of views, labels and branches in git-p4 (in contrib). 15 16 * "git-p4" (in contrib) suffered from unnecessary merge conflicts when 17 p4 expanded the embedded $RCS$-like keywords; it can be now told to 18 unexpand them. 19 20 * Some "git-svn" updates. 21 22 * "vcs-svn"/"svn-fe" learned to read dumps with svn-deltas and 23 support incremental imports. 24 25 * The configuration mechanism learned an "include" facility; an 26 assignment to the include.path pseudo-variable causes the named 27 file to be included in-place when Git looks up configuration 28 variables. 29 30 * A content filter (clean/smudge) used to be just a way to make the 31 recorded contents "more useful", and allowed to fail; a filter can 32 new optionally be marked as "required". 33 34 * "git am" learned to pass "-b" option to underlying "git mailinfo", so 35 that bracketed string other than "PATCH" at the beginning can be kept. 36 37 * "git clone" learned "--single-branch" option to limit cloning to a 38 single branch (surprise!). 39 40 * "git clone" learned to detach the HEAD in the resulting repository 41 when the source repository's HEAD does not point to a branch. 42 43 * When showing a patch while ignoring whitespace changes, the context 44 lines are taken from the postimage, in order to make it easier to 45 view the output. 46 47 * "diff-highlight" filter (in contrib/) was updated to produce more 48 aesthetically pleasing output. 49 50 * "git merge" in an interactive session learned to spawn the editor 51 by default to let the user edit the auto-generated merge message, 52 to encourage people to explain their merges better. Legacy scripts 53 can export GIT_MERGE_AUTOEDIT=no to retain the historical behavior. 54 Both "git merge" and "git pull" can be given --no-edit from the 55 command line to accept the auto-generated merge message. 56 57 * "git push" learned the "--prune" option, similar to "git fetch". 58 59 * "git tag --list" can be given "--points-at <object>" to limit its 60 output to those that point at the given object. 61 62 * "gitweb" allows intermediate entries in the directory hierarchy 63 that leads to a projects to be clicked, which in turn shows the 64 list of projects inside that directory. 65 66 * "gitweb" learned to read various pieces of information for the 67 repositories lazily, instead of reading everything that could be 68 needed (including the ones that are not necessary for a specific 69 task). 70 71Performance 72 73 * During "git upload-pack" in response to "git fetch", unnecessary calls 74 to parse_object() have been eliminated, to help performance in 75 repositories with excessive number of refs. 76 77Internal Implementation (please report possible regressions) 78 79 * Recursive call chains in "git index-pack" to deal with long delta 80 chains have been flattened, to reduce the stack footprint. 81 82 * Use of add_extra_ref() API is now gone, to make it possible to 83 cleanly restructure the overall refs API. 84 85 * The command line parser of "git pack-objects" now uses parse-options 86 API. 87 88 * The test suite supports the new "test_pause" helper function. 89 90 * Parallel to the test suite, there is a beginning of performance 91 benchmarking framework. 92 93 * t/Makefile is adjusted to prevent newer versions of GNU make from 94 running tests in seemingly random order. 95 96Also contains minor documentation updates and code clean-ups. 97 98 99Fixes since v1.7.9 100------------------ 101 102Unless otherwise noted, all the fixes since v1.7.9 in the maintenance 103releases are contained in this release (see release notes to them for 104details). 105 106 * "git branch --with $that" assumed incorrectly that the user will never 107 ask the question with nonsense value in $that. 108 (merge 6c41e97 cn/maint-branch-with-bad later to maint). 109 110 * An invalid regular expression pattern given by an end user made 111 "gitweb" to return garbled response. 112 (merge 36612e4 jn/maint-gitweb-invalid-regexp later to maint). 113 114 * "git rev-list --verify-objects -q" omitted the extra verification 115 it needs to do over "git rev-list --objects -q" by mistake. 116 (merge 9899372 nd/maint-verify-objects later to maint). 117 118 * The bulk check-in codepath streamed contents that needs 119 smudge/clean filters without running them, instead of punting and 120 delegating to the codepath to run filters after slurping everything 121 to core. 122 (merge 4f22b10 jk/maint-avoid-streaming-filtered-contents later to maint). 123 124 * When the filter driver exits before reading the content before the 125 main git process writes the contents to be filtered to the pipe to 126 it, the latter could be killed with SIGPIPE instead of ignoring 127 such an event as an error. 128 (merge 6424c2a jb/filter-ignore-sigpipe later to maint). 129 130 * When a remote helper exits before reading the blank line from the 131 main git process to signal the end of commands, the latter could be 132 killed with SIGPIPE. Instead we should ignore such event as a 133 non-error. 134 (merge c34fe63 sp/smart-http-failure-to-push later to maint). 135 136 * "git bundle create" produced a corrupt bundle file upon seeing 137 commits with excessively long subject line. 138 (merge 8a557bb tr/maint-bundle-long-subject later to maint). 139 140 * "gitweb" used to drop warnings in the log file when "heads" view is 141 accessed in a repository whose HEAD does not point at a valid 142 branch. 143 144--- 145exec >/var/tmp/1 146O=v1.7.9.2-347-gbfabdfe 147echo O=$(git describe) 148git log --first-parent --oneline ^maint $O.. 149echo 150git shortlog --no-merges ^maint $O..