Documentation / RelNotes / 1.8.3.txton commit Merge branch 'lf/bundle-with-tip-wo-message' (e1a3f17)
   1Git v1.8.3 Release Notes
   2========================
   3
   4Backward compatibility notes (for Git 2.0)
   5------------------------------------------
   6
   7When "git push [$there]" does not say what to push, we have used the
   8traditional "matching" semantics so far (all your branches were sent
   9to the remote as long as there already are branches of the same name
  10over there).  In Git 2.0, the default will change to the "simple"
  11semantics that pushes the current branch to the branch with the same
  12name, only when the current branch is set to integrate with that
  13remote branch.  There is a user preference configuration variable
  14"push.default" to change this.  If you are an old-timer who is used
  15to the "matching" semantics, you can set it to "matching" to keep the
  16traditional behaviour.  If you want to live in the future early,
  17you can set it to "simple" today without waiting for Git 2.0.
  18
  19When "git add -u" and "git add -A", that does not specify what paths
  20to add on the command line is run from inside a subdirectory, these
  21commands will operate on the entire tree in Git 2.0 for consistency
  22with "git commit -a" and other commands. Because there will be no
  23mechanism to make "git add -u" behave as if "git add -u .", it is
  24important for those who are used to "git add -u" (without pathspec)
  25updating the index only for paths in the current subdirectory to start
  26training their fingers to explicitly say "git add -u ." when they mean
  27it before Git 2.0 comes.
  28
  29
  30Updates since v1.8.2
  31--------------------
  32
  33UI, Workflows & Features
  34
  35 * "git help" learned "-g" option to show the list of guides just like
  36   list of commands are given with "-a".
  37
  38 * A triangular "pull from one place, push to another place" workflow
  39   is supported better by new remote.pushdefault (overrides the
  40   "origin" thing) and branch.*.pushremote (overrides the
  41   branch.*.remote) configuration variables.
  42
  43 * "git status" learned to report that you are in the middle of a
  44   revert session, just like it does for a cherry-pick and a bisect
  45   session.
  46
  47 * The handling by "git branch --set-upstream-to" against various forms
  48   of erroneous inputs was suboptimal and has been improved.
  49
  50 * When the interactive access to git-shell is not enabled, it issues
  51   a message meant to help the system administrator to enable it.
  52   An explicit way to help the end users who connect to the service by
  53   issuing custom messages to refuse such an access has been added.
  54
  55 * In addition to the case where the user edits the log message with
  56   the "e)dit" option of "am -i", replace the "Applying: this patch"
  57   message with the final log message contents after applymsg hook
  58   munges it.
  59
  60 * "git status" suggests users to look into using --untracked=no option
  61   when it takes too long.
  62
  63 * "git status" shows a bit more information to "git status" during a
  64   rebase/bisect session.
  65
  66 * "git fetch" learned to fetch a commit at the tip of an unadvertised
  67   ref by specifying a raw object name from the command line when the
  68   server side supports this feature.
  69
  70 * "git count-objects -v" learned to report leftover temporary
  71   packfiles and other garbage in the object store.
  72
  73 * A new read-only credential helper (in contrib/) to interact with
  74   the .netrc/.authinfo files has been added.
  75
  76 * "git send-email" can be used with the credential helper system.
  77
  78 * There was no Porcelain way to say "I no longer am interested in
  79   this submodule", once you express your interest in a submodule with
  80   "submodule init".  "submodule deinit" is the way to do so.
  81
  82 * "git pull --rebase" learned to pass "-v/-q" options to underlying
  83   "git rebase".
  84
  85 * The new "--follow-tags" option tells "git push" to push relevant
  86   annotated tags when pushing branches out.
  87
  88 * "git merge" and "git pull" can optionally be told to inspect and
  89   reject when merging a commit that does not carry a trusted GPG
  90   signature.
  91
  92 * "git mergetool" now feeds files to the "p4merge" backend in the
  93   order that matches the p4 convention, where "theirs" is usually
  94   shown on the left side, which is the opposite from other backend
  95   expects.
  96
  97 * "show/log" now honors gpg.program configuration just like other
  98   parts of the code that use GnuPG.
  99
 100 * "git log" that shows the difference between the parent and the
 101   child has been optimized somewhat.
 102
 103 * "git difftool" allows the user to write into the temporary files
 104   being shown; if the user makes changes to the working tree at the
 105   same time, one of the changes has to be lost in such a case, but it
 106   tells the user what happened and refrains from overwriting the copy
 107   in the working tree.
 108
 109 * There was no good way to ask "I have a random string that came from
 110   outside world. I want to turn it into a 40-hex object name while
 111   making sure such an object exists".  A new peeling suffix ^{object}
 112   can be used for that purpose, together with "rev-parse --verify".
 113
 114
 115Performance, Internal Implementation, etc.
 116
 117 * Updates for building under msvc.
 118
 119 * The logic to coalesce the same lines removed from the parents in
 120   the output from "diff -c/--cc" has been updated, but with an O(n^2)
 121   complexity, so this might turn out to be undesirable.
 122
 123 * The code to enforce permission bits on files in $GIT_DIR/ for
 124   shared repositories have been simplified.
 125
 126 * A few codepaths knew how much data they need to put in the
 127   hashtables they use upfront, but still started from a small table
 128   repeatedly growing and rehashing.
 129
 130 * The API to walk reflog entries from the latest to older, which was
 131   necessary for operations such as "git checkout -", was cumbersome
 132   to use correctly and also inefficient.
 133
 134 * Codepaths that inspect log-message-to-be and decide when to add a
 135   new Signed-off-by line in various commands have been consolidated.
 136
 137 * The pkt-line API, implementation and its callers have been cleaned
 138   up to make them more robust.
 139
 140 * Cygwin port has a faster-but-lying lstat(2) emulation whose
 141   incorrectness does not matter in practice except for a few
 142   codepaths, and setting permission bits to directories is a codepath
 143   that needs to use a more correct one.
 144
 145 * "git checkout" had repeated pathspec matches on the same paths,
 146   which have been consolidated.  Also a bug in "git checkout dir/"
 147   that is started from an unmerged index has been fixed.
 148
 149 * A few bugfixes to "git rerere" working on corner case merge
 150   conflicts have been applied.
 151
 152
 153Also contains minor documentation updates and code clean-ups.
 154
 155
 156Fixes since v1.8.2
 157------------------
 158
 159Unless otherwise noted, all the fixes since v1.8.2 in the maintenance
 160track are contained in this release (see release notes to them for
 161details).
 162
 163 * "git log -S/-G" started paying attention to textconv filter, but
 164   there was no way to disable this.  Make it honor --no-textconv
 165   option.
 166   (merge 61690bf sr/log-SG-no-textconv later to maint).
 167
 168 * When used with "-d temporary-directory" option, "git filter-branch"
 169   failed to come back to the original working tree to perform the
 170   final clean-up procedure.
 171   (merge 9727601 jk/filter-branch-come-back-to-original later to maint).
 172
 173 * "git merge $(git rev-parse v1.8.2)" behaved quite differently from
 174   "git merge v1.8.2", as if v1.8.2 were written as v1.8.2^0 and did
 175   not pay much attention to the annotated tag payload.  Make the code
 176   notice the type of the tag object, in addition to the dwim_ref()
 177   based classification the current code uses (i.e. the name appears
 178   in refs/tags/) to decide when to special case merging of tags.
 179   (merge a38d3d7 jc/merge-tag-object later to maint).
 180
 181 * Fix 1.8.1.x regression that stopped matching "dir" (without
 182   trailing slash) to a directory "dir".
 183   (merge efa5f82 jc/directory-attrs-regression-fix later to maint-1.8.1).
 184
 185 * "git apply --whitespace=fix" was not prepared to see a line getting
 186   longer after fixing whitespaces (e.g. tab-in-indent aka Python).
 187   (merge 329b26e jc/apply-ws-fix-tab-in-indent later to maint-1.8.1).
 188
 189 * The prompt string generator (in contrib/completion/) did not notice
 190   when we are in a middle of a "git revert" session.
 191   (merge 3ee4452 rr/prompt-revert-head later to maint).
 192
 193 * "submodule summary --summary-limit" option did not support
 194   "--option=value" form.
 195   (merge 862ae6c rs/submodule-summary-limit later to maint).
 196
 197 * "index-pack --fix-thin" used an uninitialized value to compute
 198   delta depths of objects it appends to the resulting pack.
 199   (merge 57165db jk/index-pack-correct-depth-fix later to maint).
 200
 201 * "index-pack --verify-stat" used a few counters outside protection
 202   of mutex, possibly showing incorrect numbers.
 203   (merge 8f82aad nd/index-pack-threaded-fixes later to maint).
 204
 205 * The code to keep track of what directory names are known to Git on
 206   platforms with case insensitive filesystems can get confused upon a
 207   hash collision between these pathnames and looped forever.
 208
 209 * Annotated tags outside refs/tags/ hierarchy were not advertised
 210   correctly to the ls-remote and fetch with recent version of Git.
 211
 212 * Recent optimization broke shallow clones.
 213   (merge f59de5d jk/peel-ref later to maint).
 214
 215 * "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and
 216   instead the parser kept reading beyond the end of the string.
 217
 218 * "git tag -f <tag>" always said "Updated tag '<tag>'" even when
 219   creating a new tag (i.e. not overwriting nor updating).
 220
 221 * "git p4" did not behave well when the path to the root of the P4
 222   client was not its real path.
 223   (merge bbd8486 pw/p4-symlinked-root later to maint).
 224
 225 * "git archive" reports a failure when asked to create an archive out
 226   of an empty tree.  It would be more intuitive to give an empty
 227   archive back in such a case.
 228
 229 * When "format-patch" quoted a non-ascii strings on the header files,
 230   it incorrectly applied rfc2047 and chopped a single character in
 231   the middle of it.
 232
 233 * An aliased command spawned from a bare repository that does not say
 234   it is bare with "core.bare = yes" is treated as non-bare by mistake.
 235
 236 * In "git reflog expire", REACHABLE bit was not cleared from the
 237   correct objects.
 238
 239 * The logic used by "git diff -M --stat" to shorten the names of
 240   files before and after a rename did not work correctly when the
 241   common prefix and suffix between the two filenames overlapped.
 242
 243 * The "--match=<pattern>" option of "git describe", when used with
 244   "--all" to allow refs that are not annotated tags to be used as a
 245   base of description, did not restrict the output from the command
 246   to those that match the given pattern.
 247
 248 * Clarify in the documentation "what" gets pushed to "where" when the
 249   command line to "git push" does not say these explicitly.
 250
 251 * The "--color=<when>" argument to the commands in the diff family
 252   was described poorly.
 253
 254 * The arguments given to pre-rebase hook were not documented.
 255
 256 * The v4 index format was not documented.
 257
 258 * The "--match=<pattern>" argument "git describe" takes uses glob
 259   pattern but it wasn't obvious from the documentation.
 260
 261 * Some sources failed to compile on systems that lack NI_MAXHOST in
 262   their system header (e.g. z/OS).
 263
 264 * Add an example use of "--env-filter" in "filter-branch"
 265   documentation.
 266
 267 * "git bundle verify" did not say "records a complete history" for a
 268   bundle that does not have any prerequisites.
 269
 270 * In the v1.8.0 era, we changed symbols that do not have to be global
 271   to file scope static, but a few functions in graph.c were used by
 272   CGit from sideways bypassing the entry points of the API the
 273   in-tree users use.
 274
 275 * "git update-index -h" did not do the usual "-h(elp)" thing.
 276
 277 * "git index-pack" had a buffer-overflow while preparing an
 278   informational message when the translated version of it was too
 279   long.
 280
 281 * 'git commit -m "$msg"' used to add an extra newline even when
 282   $msg already ended with one.
 283
 284 * The SSL peer verification done by "git imap-send" did not ask for
 285   Server Name Indication (RFC 4366), failing to connect SSL/TLS
 286   sites that serve multiple hostnames on a single IP.
 287
 288 * perl/Git.pm::cat_blob slurped everything in core only to write it
 289   out to a file descriptor, which was not a very smart thing to do.
 290
 291 * "git branch" did not bother to check nonsense command line
 292   parameters and issue errors in many cases.
 293
 294 * Verification of signed tags were not done correctly when not in C
 295   or en/US locale.
 296
 297 * Some platforms and users spell UTF-8 differently; retry with the
 298   most official "UTF-8" when the system does not understand the
 299   user-supplied encoding name that are the common alternative
 300   spellings of UTF-8.
 301
 302 * When export-subst is used, "zip" output recorded incorrect
 303   size of the file.
 304
 305 * "git am $maildir/" applied messages in an unexpected order; sort
 306   filenames read from the maildir/ in a way that is more likely to
 307   sort messages in the order the writing MUA meant to, by sorting
 308   numeric segment in numeric order and non-numeric segment in
 309   alphabetical order.
 310
 311 * "git submodule update", when recursed into sub-submodules, did not
 312   accumulate the prefix paths.