undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update draft release notes to 1.9

Browse Source 
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Junio C Hamano 2014-01-13 11:39:09 -08:00
parent e8a2f5f271
commit 864085aaf6
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Documentation/RelNotes/1.9.txt
View File

@ -90,6 +90,10 @@ Foreign interfaces, subsystems and ports.
UI, Workflows & Features UI, Workflows & Features
* Just like we give a reasonable default for "less" via the LESS
environment variable, we now specify a reasonable default for "lv"
via the "LV" environment variable when spawning the pager.
* Two-level configuration variable names in "branch.*" and "remote.*" * Two-level configuration variable names in "branch.*" and "remote.*"
hierarchies, whose variables are predominantly three-level, were hierarchies, whose variables are predominantly three-level, were
not completed by hitting a <TAB> in bash and zsh completions. not completed by hitting a <TAB> in bash and zsh completions.
@ -154,6 +158,13 @@ UI, Workflows & Features
Performance, Internal Implementation, etc. Performance, Internal Implementation, etc.
* When parsing a 40-hex string into the object name, the string is
checked to see if it can be interpreted as a ref so that a warning
can be given for ambiguity. The code kicked in even when the
core.warnambiguousrefs is set to false to squelch this warning, in
which case the cycles spent to look at the ref namespace were an
expensive no-op, as the result was discarded without being used.
* The naming convention of the packfiles has been updated; it used to * The naming convention of the packfiles has been updated; it used to
be based on the enumeration of names of the objects that are be based on the enumeration of names of the objects that are
contained in the pack, but now it also depends on how the packed contained in the pack, but now it also depends on how the packed
@ -197,6 +208,10 @@ Unless otherwise noted, all the fixes since v1.8.5 in the maintenance
track are contained in this release (see the maintenance releases' notes track are contained in this release (see the maintenance releases' notes
for details). for details).
* The implementation of 'git stash $cmd "stash@{...}"' did not quote
the stash argument properly and left it split at IFS whitespace.
(merge 2a07e43 ow/stash-with-ifs later to maint).
* The "--[no-]informative-errors" options to "git daemon" were parsed * The "--[no-]informative-errors" options to "git daemon" were parsed
a bit too loosely, allowing any other string after these option a bit too loosely, allowing any other string after these option
names. names.