Team Foundation Server 2015 (tfs2015) 在 orgin/remote 上运行 git gc --prune=now [英] Team Foundation Server 2015 (tfs2015) run git gc --prune=now on orgin/remote

问题描述

有没有办法在远程 Team Foundation Server 2015 (tfs2015) 上运行 git gc --prune=now?或者是在本地运行 git gc --prune=now 然后在 tfs2015 上创建新存储库并将其推送到新远程的唯一方法，然后删除旧存储库，并将新存储库重命名为旧名称.这样做时不要忘记关闭喜欢的提交.

Is there a way to run git gc --prune=now on remote Team Foundation Server 2015 (tfs2015)? Or is the only way to run git gc --prune=now locally then create new repository on tfs2015 and push it to new remote, then delete the old repository, and rename new repository to old name. Don't forget to turn off the liking commit when doing that.

推荐答案

关于在 TFS v.Next 中引入此内容的更新并且所有准备在 VSTS 中推出 https://blogs.msdn.microsoft.com/congyiw/2015/12/14/why-does-cloning-from-vsts-return-old-unreferenced-objects/更新(2017-08-09):我们向 VSTS 推出了提交可达性位图索引，并删除了下面提到的克隆作弊.克隆将不再下载无法访问的对象！.我们在服务器上还没有真正的对象级 git gc，但是现在克隆的大小会更小.

Update about comming this in TFS v.Next And all ready rolled out in VSTS https://blogs.msdn.microsoft.com/congyiw/2015/12/14/why-does-cloning-from-vsts-return-old-unreferenced-objects/ "UPDATE (2017-08-09): We rolled out commit reachability bitmap indexes to VSTS and removed the clone cheat mentioned below. Cloning will no longer download unreachable objects!. We still don't have true object-level git gc on the server yet, but clone sizes will be smaller now.

本地 TFS 将在 v.Next 中获得这些更改(不是在任何 TFS 2017 更新中，而是在下一个主要版本中).正如布赖恩·哈里 (Brian Harry) 所提到的，我们应该会在几周内为 v.Next 提供一个候选版本."

TFS on-prem will get these changes in v.Next (not in any TFS 2017 updates, but the next major release). As Brian Harry mentioned, we should have a release candidate for v.Next in a few weeks."

这篇关于Team Foundation Server 2015 (tfs2015) 在 orgin/remote 上运行 git gc --prune=now的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！