Update draft release notes to 1.7.4.2
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
@ -7,6 +7,11 @@ Fixes since v1.7.4.1
|
|||||||
* Many documentation updates to match "git cmd -h" output and the
|
* Many documentation updates to match "git cmd -h" output and the
|
||||||
git-cmd manual page.
|
git-cmd manual page.
|
||||||
|
|
||||||
|
* We used to keep one file descriptor open for each and every packfile
|
||||||
|
that we have a mmap window on it (read: "in use"), even when for very
|
||||||
|
tiny packfiles. We now close the file descriptor early when the entire
|
||||||
|
packfile fits inside one mmap window.
|
||||||
|
|
||||||
* "git clone /no/such/path" did not fail correctly.
|
* "git clone /no/such/path" did not fail correctly.
|
||||||
|
|
||||||
* "git commit" did not correctly error out when the user asked to use a
|
* "git commit" did not correctly error out when the user asked to use a
|
||||||
@ -34,6 +39,10 @@ Fixes since v1.7.4.1
|
|||||||
to update the upstream branch it forked from is now called "upstream".
|
to update the upstream branch it forked from is now called "upstream".
|
||||||
The old name "tracking" is and will be supported.
|
The old name "tracking" is and will be supported.
|
||||||
|
|
||||||
|
* "git submodule update" used to honor the --merge/--rebase option (or
|
||||||
|
corresponding configuration variables) even for a newly cloned
|
||||||
|
subproject, which made no sense (so/submodule-no-update-first-time).
|
||||||
|
|
||||||
* gitweb's "highlight" interface mishandled tabs.
|
* gitweb's "highlight" interface mishandled tabs.
|
||||||
|
|
||||||
* gitweb had a few forward-incompatible syntactic constructs and
|
* gitweb had a few forward-incompatible syntactic constructs and
|
||||||
|
Reference in New Issue
Block a user