Andrew's git - gitweb.git/blob - Documentation/RelNotes/1.7.10.txt

   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 * 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
  17   variables.
  18
  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".
  22
  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".
  26
  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.
  29
  30 * "git clone" learned "--single-branch" option to limit cloning to a
  31   single branch (surprise!).
  32
  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.
  35
  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
  38   view the output.
  39
  40 * "diff-highlight" filter (in contrib/) was updated to produce more
  41   aesthetically pleasing output.
  42
  43 * "fsck" learned "--no-dangling" option to omit dangling object
  44   information.
  45
  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.
  52
  53 * "git push" learned the "--prune" option, similar to "git fetch".
  54
  55 * "git tag --list" can be given "--points-at <object>" to limit its
  56   output to those that point at the given object.
  57
  58 * "gitweb" allows intermediate entries in the directory hierarchy
  59   that leads to a projects to be clicked, which in turn shows the
  60   list of projects inside that directory.
  61
  62 * "gitweb" learned to read various pieces of information for the
  63   repositories lazily, instead of reading everything that could be
  64   needed (including the ones that are not necessary for a specific
  65   task).
  66
  67Foreign Interface
  68
  69 * Improved handling of views, labels and branches in git-p4 (in contrib).
  70
  71 * "git-p4" (in contrib) suffered from unnecessary merge conflicts when
  72   p4 expanded the embedded $RCS$-like keywords; it can be now told to
  73   unexpand them.
  74
  75 * Some "git-svn" updates.
  76
  77 * "vcs-svn"/"svn-fe" learned to read dumps with svn-deltas and
  78   support incremental imports.
  79
  80Performance
  81
  82 * During "git upload-pack" in response to "git fetch", unnecessary calls
  83   to parse_object() have been eliminated, to help performance in
  84   repositories with excessive number of refs.
  85
  86Internal Implementation (please report possible regressions)
  87
  88 * Recursive call chains in "git index-pack" to deal with long delta
  89   chains have been flattened, to reduce the stack footprint.
  90
  91 * Use of add_extra_ref() API is now gone, to make it possible to
  92   cleanly restructure the overall refs API.
  93
  94 * The command line parser of "git pack-objects" now uses parse-options
  95   API.
  96
  97 * The test suite supports the new "test_pause" helper function.
  98
  99 * Parallel to the test suite, there is a beginning of performance
 100   benchmarking framework.
 101
 102 * t/Makefile is adjusted to prevent newer versions of GNU make from
 103   running tests in seemingly random order.
 104
 105Also contains minor documentation updates and code clean-ups.
 106
 107
 108Fixes since v1.7.9
 109------------------
 110
 111Unless otherwise noted, all the fixes since v1.7.9 in the maintenance
 112releases are contained in this release (see release notes to them for
 113details).
 114
 115 * "git branch --with $that" assumed incorrectly that the user will never
 116   ask the question with nonsense value in $that.
 117   (merge 6c41e97 cn/maint-branch-with-bad later to maint).
 118
 119 * An invalid regular expression pattern given by an end user made
 120   "gitweb" to return garbled response.
 121   (merge 36612e4 jn/maint-gitweb-invalid-regexp later to maint).
 122
 123 * "git rev-list --verify-objects -q" omitted the extra verification
 124   it needs to do over "git rev-list --objects -q" by mistake.
 125   (merge 9899372 nd/maint-verify-objects later to maint).
 126
 127 * The bulk check-in codepath streamed contents that needs
 128   smudge/clean filters without running them, instead of punting and
 129   delegating to the codepath to run filters after slurping everything
 130   to core.
 131   (merge 4f22b10 jk/maint-avoid-streaming-filtered-contents later to maint).
 132
 133 * When the filter driver exits before reading the content before the
 134   main git process writes the contents to be filtered to the pipe to
 135   it, the latter could be killed with SIGPIPE instead of ignoring
 136   such an event as an error.
 137   (merge 6424c2a jb/filter-ignore-sigpipe later to maint).
 138
 139 * When a remote helper exits before reading the blank line from the
 140   main git process to signal the end of commands, the latter could be
 141   killed with SIGPIPE. Instead we should ignore such event as a
 142   non-error.
 143   (merge c34fe63 sp/smart-http-failure-to-push later to maint).
 144
 145 * "git bundle create" produced a corrupt bundle file upon seeing
 146   commits with excessively long subject line.
 147   (merge 8a557bb tr/maint-bundle-long-subject later to maint).
 148
 149 * "gitweb" used to drop warnings in the log file when "heads" view is
 150   accessed in a repository whose HEAD does not point at a valid
 151   branch.
 152
 153---
 154exec >/var/tmp/1
 155O=v1.7.9.2-358-g64d1544
 156echo O=$(git describe)
 157git log --first-parent --oneline ^maint $O..
 158echo
 159git shortlog --no-merges ^maint $O..