Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
git
提交
cac25fc3
G
git
项目概览
李少辉-开发者
/
git
与 Fork 源项目一致
从无法访问的项目Fork
通知
2
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
git
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
cac25fc3
编写于
7月 18, 2017
作者:
J
Junio C Hamano
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
A few more topics before 2.14-rc1
Signed-off-by:
N
Junio C Hamano
<
gitster@pobox.com
>
上级
764046f6
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
45 addition
and
19 deletion
+45
-19
Documentation/RelNotes/2.14.0.txt
Documentation/RelNotes/2.14.0.txt
+45
-19
未找到文件。
Documentation/RelNotes/2.14.0.txt
浏览文件 @
cac25fc3
Git 2.14 Release Notes
Git 2.14 Release Notes
======================
======================
Backward compatibility notes.
Backward compatibility notes
and other notable changes
.
* Use of an empty string as a pathspec element that is used for
* Use of an empty string as a pathspec element that is used for
'everything matches' is still warned and Git asks users to use a
'everything matches' is still warned and Git asks users to use a
...
@@ -22,6 +22,12 @@ Backward compatibility notes.
...
@@ -22,6 +22,12 @@ Backward compatibility notes.
diff output has finished, and the "indent heuristics" has now
diff output has finished, and the "indent heuristics" has now
become the default.
become the default.
* Git can now be built with PCRE v2 instead of v1 of the PCRE
library. Replace USE_LIBPCRE=YesPlease with USE_LIBPCRE2=YesPlease
in existing build scripts to build against the new version. As the
upstream PCRE maintainer has abandoned v1 maintenance for all but
the most critical bug fixes, use of v2 is recommended.
Updates since v2.13
Updates since v2.13
-------------------
-------------------
...
@@ -53,16 +59,16 @@ UI, Workflows & Features
...
@@ -53,16 +59,16 @@ UI, Workflows & Features
when the $sha1 names an object at the tip of an advertised ref,
when the $sha1 names an object at the tip of an advertised ref,
even when the other side hasn't enabled allowTipSHA1InWant.
even when the other side hasn't enabled allowTipSHA1InWant.
* The recently introduced "[includeIf "gitdir:$dir"] path=..."
* The "[includeIf "gitdir:$dir"] path=..." mechanism introduced in
mechanism has further been taught to take symlinks into account.
2.13.0 would canonicalize the path of the gitdir being matched,
The directory "$dir" specified in "gitdir:$dir" may be a symlink to
and did not match e.g. "gitdir:~/work/*" against a repo in
a real location, not something that $(getcwd) may return. In such
"~/work/main" if "~/work" was a symlink to "/mnt/storage/work".
a case, a realpath of "$dir" is compared with the real path of the
Now we match both the resolved canonical path and what "pwd" would
current repository to determine if the contents from the named path
show. The include will happen if either one matches.
should be included.
* Make the "indent" heuristics the default in "diff" and diff.indentHeuristics
* The "indent" heuristics is now the default in "diff". The
configuration variable an escape hatch for those who do no want it.
diff.indentHeuristic configuration variable can be set to "false"
for those who do not want it.
* Many commands learned to pay attention to submodule.recurse
* Many commands learned to pay attention to submodule.recurse
configuration.
configuration.
...
@@ -91,8 +97,8 @@ UI, Workflows & Features
...
@@ -91,8 +97,8 @@ UI, Workflows & Features
would appear as a not-quite-initialized submodule to others. We
would appear as a not-quite-initialized submodule to others. We
learned to give warnings when this happens.
learned to give warnings when this happens.
* "git status" learned to optionally give how many stash entries the
* "git status" learned to optionally give how many stash entries the
re
user has
in its output.
are
in its output.
* "git status" has long shown essentially the same message as "git
* "git status" has long shown essentially the same message as "git
commit"; the message it gives while preparing for the root commit,
commit"; the message it gives while preparing for the root commit,
...
@@ -101,9 +107,9 @@ UI, Workflows & Features
...
@@ -101,9 +107,9 @@ UI, Workflows & Features
(rather than the commit the user is preparing for, which is more in
(rather than the commit the user is preparing for, which is more in
line with the focus of "git commit").
line with the focus of "git commit").
* "git send-email"
learned to overcome some SMTP server limitation
* "git send-email"
now has --batch-size and --relogin-delay options
that does not allow many pieces of e-mails to be sent over a single
which can be used to overcome limitations on SMTP servers that
session.
restrict on how many of e-mails can be sent in a single
session.
* An old message shown in the commit log template was removed, as it
* An old message shown in the commit log template was removed, as it
has outlived its usefulness.
has outlived its usefulness.
...
@@ -425,19 +431,17 @@ notes for details).
...
@@ -425,19 +431,17 @@ notes for details).
* A recent regression in "git rebase -i" has been fixed and tests
* A recent regression in "git rebase -i" has been fixed and tests
that would have caught it and others have been added.
that would have caught it and others have been added.
* An unaligned 32-bit access in pack-bitmap code
ah
s been corrected.
* An unaligned 32-bit access in pack-bitmap code
ha
s been corrected.
* Tighten error checks for invalid "git apply" input.
* Tighten error checks for invalid "git apply" input.
* The split index code did not honor core.shared
r
epository setting
* The split index code did not honor core.shared
R
epository setting
correctly.
correctly.
* The Makefile rule in contrib/subtree for building documentation
* The Makefile rule in contrib/subtree for building documentation
learned to honour USE_ASCIIDOCTOR just like the main documentation
learned to honour USE_ASCIIDOCTOR just like the main documentation
set does.
set does.
* Update the sha1dc again to fix portability glitches.
* Code clean-up to fix possible buffer over-reading.
* Code clean-up to fix possible buffer over-reading.
(merge 2d105451c0 rs/apply-avoid-over-reading later to maint).
(merge 2d105451c0 rs/apply-avoid-over-reading later to maint).
...
@@ -461,6 +465,28 @@ notes for details).
...
@@ -461,6 +465,28 @@ notes for details).
Git with address sanitizer more easily.
Git with address sanitizer more easily.
(merge 566cf0b3bd jk/build-with-asan later to maint).
(merge 566cf0b3bd jk/build-with-asan later to maint).
* On Cygwin, similar to Windows, "git push //server/share/repository"
ought to mean a repository on a network share that can be accessed
locally, but this did not work correctly due to stripping the double
slashes at the beginning.
(merge 496f256989 tb/push-to-cygwin-unc-path later to maint).
* The progress meter did not give a useful output when we haven't had
0.5 seconds to measure the throughput during the interval. Instead
show the overall throughput rate at the end, which is a much more
useful number.
(merge 0fae1e072a rs/progress-overall-throughput-at-the-end later to maint).
* Code clean-up, that makes us in sync with Debian by one patch.
(merge 8db1ae5740 jn/hooks-pre-rebase-sample-fix later to maint).
* We run an early part of "git gc" that deals with refs before
daemonising (and not under lock) even when running a background
auto-gc, which caused multiple gc processes attempting to run the
early part at the same time. This is now prevented by running the
early part also under the GC lock.
(merge c45af94dbc jk/gc-pre-detach-under-hook later to maint).
* Other minor doc, test and build updates and code cleanups.
* Other minor doc, test and build updates and code cleanups.
(merge 3f9c637ec7 pw/unquote-path-in-git-pm later to maint).
(merge 3f9c637ec7 pw/unquote-path-in-git-pm later to maint).
(merge 5053313562 rs/urlmatch-cleanup later to maint).
(merge 5053313562 rs/urlmatch-cleanup later to maint).
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录