设为首页 收藏本站
查看: 772|回复: 0

[经验分享] Git 2.6.3 发布,bug 修复版本

[复制链接]

尚未签到

发表于 2015-11-22 09:49:10 | 显示全部楼层 |阅读模式
欢迎加入运维网交流群:263444886   DSC0000.jpg
DSC0001.png   Git 2.6.3 发布,主要是 bug 修复:
  * The error message from "git blame --contents --reverse" incorrectly
  talked about "--contents --children".
  
  * "git merge-file" tried to signal how many conflicts it found, which
  obviously would not work well when there are too many of them.
  
  * The name-hash subsystem that is used to cope with case insensitive
  filesystems keeps track of directories and their on-filesystem
  cases for all the paths in the index by holding a pointer to a
  randomly chosen cache entry that is inside the directory (for its
  ce->ce_name component).  This pointer was not updated even when the
  cache entry was removed from the index, leading to use after free.
  This was fixed by recording the path for each directory instead of
  borrowing cache entries and restructuring the API somewhat.
  
  * When the "git am" command was reimplemented in C, "git am -3" had a
  small regression where it is aborted in its error handling codepath
  when underlying merge-recursive failed in some ways.
  
  * The synopsis text and the usage string of subcommands that read
  list of things from the standard input are often shown as if they
  only take input from a file on a filesystem, which was misleading.
  
  * A couple of commands still showed "[options]" in their usage string
  to note where options should come on their command line, but we
  spell that "[]" in most places these days.
  
  * The submodule code has been taught to work better with separate
  work trees created via "git worktree add".
  
  * When "git gc --auto" is backgrounded, its diagnosis message is
  lost.  It now is saved to a file in $GIT_DIR and is shown next time
  the "gc --auto" is run.
  
  * Work around "git p4" failing when the P4 depot records the contents
  in UTF-16 without UTF-16 BOM.
  
  * Recent update to "rebase -i" that tries to sanity check the edited
  insn sheet before it uses it has become too picky on Windows where
  CRLF left by the editor is turned into a trailing CR on the line
  read via the "read" built-in command.
  
  * "git clone --dissociate" runs a big "git repack" process at the
  end, and it helps to close file descriptors that are open on the

  packs and their>  cannot remove a file that is still open.
  
  * Correct "git p4 --detect-labels" so that it does not fail to create
  a tag that points at a commit that is also being imported.
  
  * The internal stripspace() function has been moved to where it
  logically belongs to, i.e. strbuf API, and the command line parser
  of "git stripspace" has been updated to use the parse_options API.
  
  * Prepare for Git on-disk repository representation to undergo
  backward incompatible changes by introducing a new repository
  format version "1", with an extension mechanism.
  
  * "git gc" used to barf when a symbolic ref has gone dangling
  (e.g. the branch that used to be your upstream's default when you
  cloned from it is now gone, and you did "fetch --prune").
  
  * The normalize_ceiling_entry() function does not muck with the end

  of the path it accepts, and the real world callers do>  but a test insisted that the function drops a trailing slash.
  
  * "git gc" is safe to run anytime only because it has the built-in
  grace period to protect young objects.  In order to run with no
  grace period, the user must make sure that the repository is
  quiescent.
  
  * A recent "filter-branch --msg-filter" broke skipping of the commit
  object header, which is fixed.
  
  * "git --literal-pathspecs add -u/-A" without any command line
  argument misbehaved ever since Git 2.0.
  
  * Merging a branch that removes a path and another that changes the
  mode bits on the same path should have conflicted at the path, but
  it didn't and silently favoured the removal.
  
  * "git imap-send" did not compile well with older version of cURL library.
  
  * The linkage order of libraries was wrong in places around libcurl.
  
  * It was not possible to use a repository-lookalike created by "git
  worktree add" as a local source of "git clone".
  
  * When "git send-email" wanted to talk over Net::SMTP::SSL,
  Net::Cmd::datasend() did not like to be fed too many bytes at the
  same time and failed to send messages.  Send the payload one line
  at a time to work around the problem.
  
  * We peek objects from submodule's object store by linking it to the

  list of>  correctly initialize the list.
  
  * "git status --branch --short" accessed beyond the constant string
  "HEAD", which has been corrected.
  
  * "git daemon" uses "run_command()" without "finish_command()", so it

  needs to>  下载:https://github.com/git/git/archive/v2.6.3.zip
  
  Git是一个开源的分布式版本控制系统,用以有效、高速的处理从很小到非常大的项目版本管理。
  开源中国 Git 代码托管平台:http://git.oschina.net/
DSC0002.jpg

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-142024-1-1.html 上篇帖子: GitLab 8.1.3 发布,代码托管平台 下篇帖子: TortoiseGit 1.8.16.0 发布,Git 客户端
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表