使用 Trac 查找哪些文件被“修复”以及两个特定日期之间有多少次？
我需要找出由于使用 Trac 的开源项目中两个特定日期之间的错误而修复或更改了多少次以及哪些文件。为此我选择了 Webkit 项目。 (https://trac.webkit.org/) 但是，它可以是任何开源项目。
我能为此做些什么呢？我该如何开始？我是否必须使用 svn 或 git 等版本控制系统进行集成？我对这些错误跟踪和问题跟踪系统有点新手。
I need to find out that how many times and which files are fixed or changed due to a bug between two specific dates in an open source project which uses Trac. I selected Webkit project for that purpose. (https://trac.webkit.org/) However, it can be any open source project.
What can I do for that? How do I start? Do i have to use version control systems like svn or git for intergration? I am kinda newbie for these bug-tracking and issue-tracking systems.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不确定我是否完全理解您的问题，但是...
如果您在 Trac 站点中浏览到包含您关心的文件的目录，然后单击
修订日志，您将获得一个列表影响该目录的变更集。您可以选择跨越感兴趣的时间范围的修订，然后查看更改，您将获得更改的摘要，并且根据更改的大小和特定的 Trac 配置，您可能会获得该页面上也有差异。现在，这不会告诉您这些文件被更改了多少次，而只是净更改次数。
它也不会告诉您这些更改是针对哪些错误。
如果您确实需要过滤哪些错误，则必须确定特定项目如何跟踪该信息；有些可能不会直接跟踪它。该项目可能会在提交消息中包含
#123。如果您可以信赖这一点，您可以使用 svn log --xml {2009-11-01}:{2009-12-01} ... 获取提交日志的 xml 版本，其中然后，您可以根据提交消息中存在的错误票号进行解析和过滤。由此，您应该有一个您关心的修订的列表。I'm not certain I exactly understand your question, but...
If you browse to the directory containing the files you care about in the Trac site, then click on
Revision Log, you will get a list of changesets that affected that directory. You can select the revisions that span the timeframe of interest and thenView changesand you will get a summary of the changes, and depending on the size of the changes and the particular Trac configuration, you may get the diffs on that page as well.Now, that won't tell you how many times those files were changed, just the net changes.
It also won't tell you which bugs those changes were for.
If you really need to filter on what bug, you'll have to determine how that information is tracked by the particular project; and some might not track it directly. The project might include a
#123in the commit message. If you can rely on that, you could usesvn log --xml {2009-11-01}:{2009-12-01} ...to get an xml version of the commit log which you could then parse and filter based on the presence of the bug's ticket number in the commit message. From that, you should have a list of the revisions that you care about.