@ -281,6 +281,11 @@ notes for details).
|
|||||||
listing and sparse checkout selection areas in 2.7.0; the change
|
listing and sparse checkout selection areas in 2.7.0; the change
|
||||||
that is responsible for the regression has been reverted.
|
that is responsible for the regression has been reverted.
|
||||||
|
|
||||||
|
* Another try to improve the ignore mechanism that lets you say "this
|
||||||
|
is excluded" and then later say "oh, no, this part (that is a
|
||||||
|
subset of the previous part) is not excluded". This has still a
|
||||||
|
known limitation, though.
|
||||||
|
|
||||||
* Some codepaths used fopen(3) when opening a fixed path in $GIT_DIR
|
* Some codepaths used fopen(3) when opening a fixed path in $GIT_DIR
|
||||||
(e.g. COMMIT_EDITMSG) that is meant to be left after the command is
|
(e.g. COMMIT_EDITMSG) that is meant to be left after the command is
|
||||||
done. This however did not work well if the repository is set to
|
done. This however did not work well if the repository is set to
|
||||||
@ -372,10 +377,6 @@ notes for details).
|
|||||||
misbehaved when run from a subdirectory.
|
misbehaved when run from a subdirectory.
|
||||||
(merge 17f1365 nd/git-common-dir-fix later to maint).
|
(merge 17f1365 nd/git-common-dir-fix later to maint).
|
||||||
|
|
||||||
* Another try to add support to the ignore mechanism that lets you
|
|
||||||
say "this is excluded" and then later say "oh, no, this part (that
|
|
||||||
is a subset of the previous part) is not excluded".
|
|
||||||
|
|
||||||
* "git worktree add -B <branchname>" did not work.
|
* "git worktree add -B <branchname>" did not work.
|
||||||
|
|
||||||
* The "v(iew)" subcommand of the interactive "git am -i" command was
|
* The "v(iew)" subcommand of the interactive "git am -i" command was
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
#!/bin/sh
|
#!/bin/sh
|
||||||
|
|
||||||
GVF=GIT-VERSION-FILE
|
GVF=GIT-VERSION-FILE
|
||||||
DEF_VER=v2.8.0-rc1
|
DEF_VER=v2.8.0-rc2
|
||||||
|
|
||||||
LF='
|
LF='
|
||||||
'
|
'
|
||||||
|
Reference in New Issue
Block a user