bd3b89dae278074bbafbbd94b3fc3ea9f782128a
   1Git v1.8.0 Release Notes
   2========================
   3
   4Backward compatibility notes
   5----------------------------
   6
   7In the next major release, we will change the behaviour of the "git
   8push" command.  When "git push [$there]" does not say what to push, we
   9have used the traditional "matching" semantics (all your branches were
  10sent to the remote as long as there already are branches of the same
  11name over there).  We will use the "simple" semantics, that pushes the
  12current branch to the branch with the same name only when the current
  13branch is set to integrate with that remote branch.  There is a user
  14preference configuration variable "push.default" to change this, and
  15"git push" will warn about the upcoming change until you set this
  16variable.
  17
  18"git branch --set-upstream" is deprecated and may be removed in a
  19relatively distant future.  "git branch [-u|--set-upstream-to]" has
  20been introduced with a saner order of arguments.
  21
  22
  23Updates since v1.7.12
  24---------------------
  25
  26UI, Workflows & Features
  27
  28 * A credential helper for Win32 to allow access to the keychain of
  29   the logged-in user has been added.
  30
  31 * A credential helper to allow access to the Gnome keyring has been
  32   added.
  33
  34 * It was tempting to say "git branch --set-upstream origin/master",
  35   but that tells Git to arrange the local branch "origin/master" to
  36   integrate with the currently checked out branch, which is highly
  37   unlikely what the user meant.  The option is deprecated; use the
  38   new "--set-upstream-to" (with a short-and-sweet "-u") option
  39   instead.
  40
  41 * "git cherry-pick" learned the "--allow-empty-message" option to
  42   allow it to replay a commit without any log message.
  43
  44 * "git daemon" learned the "--access-hook" option to allow an
  45   external command to decline service based on the client address,
  46   repository path, etc.
  47
  48 * "git difftool --dir-diff" learned to use symbolic links to prepare
  49   temporary copy of the working tree when available.
  50
  51 * "git grep" learned to use a non-standard pattern type by default if
  52   a configuration variable tells it to.
  53
  54Foreign Interface
  55
  56 * "git svn" has been updated to work with SVN 1.7.
  57
  58Performance, Internal Implementation, etc. (please report possible regressions)
  59
  60 * The "check-docs" build target has been updated and greatly
  61   simplified.
  62
  63 * The documentation in the TeXinfo format was using indented output
  64   for materials meant to be examples that are better typeset in
  65   monospace.
  66
  67 * Compatibility wrapper to learn the maximum number of file
  68   descriptors we can open around sysconf(_SC_OPEN_MAX) and
  69   getrlimit(RLIMIT_NO_FILE) has been introduced for portability.
  70
  71 * Compatibility wrapper around some mkdir(2) implementations that
  72   reject parameter with trailing slash has been introduced.
  73
  74 * The heuristics to detect and silently convert latin1 to utf8 when
  75   we were told to use utf-8 in the log message has been transplanted
  76   from "mailinfo" to "commit" and "commit-tree".
  77
  78 * Messages given by "git <subcommand> -h" from many subcommands have
  79   been marked for translation.
  80
  81Also contains minor documentation updates and code clean-ups.
  82
  83
  84Fixes since v1.7.12
  85-------------------
  86
  87Unless otherwise noted, all the fixes since v1.7.12 in the
  88maintenance track are contained in this release (see release notes
  89to them for details).
  90
  91 * "git cherry-pick A C B" used to replay changes in A and then B and
  92   then C if these three commits had committer timestamps in that
  93   order, which is not what the user who said "A C B" naturally
  94   expects.
  95   (merge a73e22e mz/cherry-pick-cmdline-order later to maint).
  96
  97 * "git show --quiet" ought to be a synonym for "git show -s", but
  98   wasn't.
  99   (merge f9c75d8 jk/maint-quiet-is-synonym-to-s-in-log later to maint).
 100
 101 * "git p4", when "--use-client-spec" and "--detect-branches" are used
 102   together, misdetected branches.
 103   (merge 21ef5df pw/p4-use-client-spec-branch-detection later to maint).
 104
 105 * Output from "git branch -v" contains "(no branch)" that could be
 106   localized, but the code to align it along with the names of
 107   branches were counting in bytes, not in display columns.
 108   (merge 1452bd6 nd/branch-v-alignment later to maint).
 109
 110 * "git for-each-ref" did not currectly support more than one --sort
 111   option.
 112   (merge 3b51222 kk/maint-for-each-ref-multi-sort later to maint).
 113
 114 * Pushing to smart HTTP server with recent Git fails without having
 115   the username in the URL to force authentication, if the server is
 116   configured to allow GET anonymously, while requiring authentication
 117   for POST.
 118   (merge b81401c jk/maint-http-half-auth-push later to maint).
 119
 120 * When looking for $HOME/.gitconfig etc., it is OK if we cannot read
 121   them because they do not exist, but we did not diagnose existing
 122   files that we cannot read.
 123
 124 * The synopsis said "checkout [-B branch]" to make it clear the
 125   branch name is a parameter to the option, but the heading for the
 126   option description was "-B::", not "-B branch::", making the
 127   documentation misleading.  There may be room in documentation pages
 128   of other commands for similar improvements (hint, hint).
 129   (merge 45aaf03 jc/maint-doc-checkout-b-always-takes-branch-name later to maint).
 130
 131 * "git log .." errored out saying it is both rev range and a path
 132   when there is no disambiguating "--" is on the command line.
 133   Update the command line parser to interpret ".." as a path in such
 134   a case.
 135   (merge 003c84f jc/dotdot-is-parent-directory later to maint).
 136
 137 * "git apply -p0" did not parse pathnames on "diff --git" line
 138   correctly.  This caused patches that had pathnames in no other
 139   places to be mistakenly rejected (most notably, binary patch that
 140   does not rename nor change mode).  Textual patches, renames or mode
 141   changes have preimage and postimage pathnames in different places
 142   in a form that can be parsed unambiguously and did not suffer from
 143   this problem.
 144   (merge 6a2abdc jc/apply-binary-p0 later to maint).
 145
 146 * The exit status code from "git config" was way overspecified while
 147   being incorrect.  The implementation has been updated to give the
 148   documented status for a case that was documented, and introduce a
 149   new code for "all other errors".
 150   (merge 9409c7a jc/maint-config-exit-status later to maint).
 151
 152 * "git foo" errored out with "Not a directory" when the user had a
 153   non-directory on $PATH, and worse yet it masked an alias "foo" from
 154   running.  (merge a785508 jc/maint-sane-execvp-notdir later to
 155   maint).
 156
 157 * The interactive prompt "git send-email" gives was error prone. It
 158   asked "What e-mail address do you want to use?" with the address it
 159   guessed (correctly) the user would want to use in its prompt,
 160   tempting the user to say "y". But the response was taken as "No,
 161   please use 'y' as the e-mail address instead", which is most
 162   certainly not what the user meant.
 163   (merge 51bbccf jc/send-email-reconfirm later to maint).
 164
 165 * "git stash apply/pop" did not trigger "rerere" upon conflicts
 166   unlike other mergy operations.
 167   (merge 743bf6d ph/stash-rerere later to maint).
 168
 169 * "git submodule update -f" did not update paths in the working tree
 170   that has local changes.
 171   (merge 01d4721 sz/submodule-force-update later to maint).
 172
 173 * We used curl_easy_strerror() without checking version of cURL,
 174   breaking the build for versions before curl 7.12.0.
 175   (merge 4246b0b js/no-curl-easy-strerror-on-old-curl later to maint).
 176
 177 * Code to work around MacOS X UTF-8 gotcha has been cleaned up.
 178   (merge 9a27f96 rr/precompose-utf8-cleanup later to maint).
 179
 180 * Documentation for the configuration file format had a confusing
 181   example.
 182   (merge d1e1fe7 mh/maint-config-doc-proxy-command later to maint).
 183
 184 * "git submodule <cmd> path" did not error out when the path to the
 185   submodule was misspelt.
 186   (merge be9d0a3 hv/submodule-path-unmatch later to maint).
 187
 188 * Some capabilities were asked by fetch-pack even when upload-pack
 189   did not advertise that they are available.  fetch-pack has been
 190   fixed not to do so.
 191
 192 * The output from "git diff -B" for a file that ends with an
 193   incomplete line did not put "\ No newline..." on a line of its own.