Update draft release notes to 2.0
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
2d1a5a5856
commit
7bf272cc04
@ -136,7 +136,8 @@ UI, Workflows & Features
|
||||
|
||||
Performance, Internal Implementation, etc.
|
||||
|
||||
* The compilation options to port to AIX has been updated.
|
||||
* The compilation options to port to AIX and to MSVC have been
|
||||
updated.
|
||||
|
||||
* We started using wildmatch() in place of fnmatch(3) a few releases
|
||||
ago; complete the process and stop using fnmatch(3).
|
||||
@ -170,6 +171,10 @@ Unless otherwise noted, all the fixes since v1.9 in the maintenance
|
||||
track are contained in this release (see the maintenance releases'
|
||||
notes for details).
|
||||
|
||||
* "git update-ref --stdin" did not fail a request to create a ref
|
||||
when the ref already existed.
|
||||
(merge b9d56b5 mh/update-ref-batch-create-fix later to maint).
|
||||
|
||||
* "git diff --no-index -Mq a b" fell into an infinite loop.
|
||||
(merge ad1c3fb jc/fix-diff-no-index-diff-opt-parse later to maint).
|
||||
|
||||
@ -190,23 +195,9 @@ notes for details).
|
||||
"ahead/behind/gone" translated to the user's locale.
|
||||
(merge 7a76c28 mm/status-porcelain-format-i18n-fix later to maint).
|
||||
|
||||
|
||||
* "git repack" died when asked to (re)pack with the reachability
|
||||
bitmap when a bitmap cannot be built; instead, just (re)pack
|
||||
without producing a bitmap in such a case, with a warning.
|
||||
(merge 373c67d jk/pack-bitmap later to maint).
|
||||
|
||||
|
||||
* The progress output while repacking and transferring objects showed
|
||||
an apparent large silence while writing the objects out of existing
|
||||
packfiles, when the reachability bitmap was in use.
|
||||
(merge 78d2214 jk/pack-bitmap-progress later to maint).
|
||||
|
||||
|
||||
* A stray environment variable $prefix could have leaked into and
|
||||
affected the behaviour of the "subtree" script (in contrib/).
|
||||
|
||||
|
||||
* When it is not necessary to edit a commit log message (e.g. "git
|
||||
commit -m" is given a message without specifying "-e"), we used to
|
||||
disable the spawning of the editor by overriding GIT_EDITOR, but
|
||||
@ -214,7 +205,6 @@ notes for details).
|
||||
commit log message, are also affected.
|
||||
(merge b549be0 bp/commit-p-editor later to maint).
|
||||
|
||||
|
||||
* "git mv" that moves a submodule forgot to adjust the array that
|
||||
uses to keep track of which submodules were to be moved to update
|
||||
its configuration.
|
||||
@ -274,7 +264,7 @@ notes for details).
|
||||
|
||||
* Codepaths that parse timestamps in commit objects have been
|
||||
tightened.
|
||||
(merge 3f419d4 jk/commit-dates-parsing-fix later to maint).
|
||||
(merge f80d1f9 jk/commit-dates-parsing-fix later to maint).
|
||||
|
||||
* "git diff --external-diff" incorrectly fed the submodule directory
|
||||
in the working tree to the external diff driver when it knew it is
|
||||
@ -329,3 +319,7 @@ notes for details).
|
||||
extra and unnecessary trailing slash (such a slash is often
|
||||
given by command line completion).
|
||||
(merge 2e70c01 nd/submodule-pathspec-ending-with-slash later to maint.)
|
||||
|
||||
* Documentation and in-code comments had many instances of mistaken
|
||||
use of "nor", which have been corrected.
|
||||
(merge 235e8d5 jl/nor-or-nand-and later to maint).
|
||||
|
Loading…
Reference in New Issue
Block a user