We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(1)
我认为不存在任何明确的工具,我想是因为同步到集中式源代码控制系统中的历史点要容易得多,所以没有人觉得需要工具。
只需同步回历史记录,直到到达不再发生回归(您试图跟踪)的点,然后同步到该点和 HEAD 之间的历史记录,直到找到问题修订。
I don't think any explicit tool exists, I guess because syncing to a point in history in a centralized source control system is much easier, so no-one has felt the need for a tool.
Just sync back in history till you reach a point where the regression (that you are trying to trace) no longer happens, then sync to history between that point and HEAD, until you find the problem revision.