TFS提交未更改的文件 [英] TFS commits unchanged files
问题描述
我们正在使用MS Visual Studio 2008。
We're using MS Visual Studio 2008.
TFS似乎考虑了文件的创建日期或其他内容，以确定是否应提交文件。
TFS seems to take into account the creation date of a file or something, to determine whether the files should be committed.
是否可以仅对文件名和内容进行TFS测试？
Is it possible to make TFS test just on the filename and content?
- 我签出xml或txt文件
- 复制内容
- 我打开记事本并粘贴
- 我使用相同的名称保存文件，并确认覆盖
- 我提交：TFS 默认情况下选择要提交的文件
- I check out an xml or txt file
- I copy the content
- I open notepad and paste
- I save the file using the same name, and confirm the overwrite
- I commit: TFS by default selects the file for committing
尽管名称或内容已更改。
Although the name nor the content has changed.
我们的具体用例：
我们每晚运行一个脚本，该脚本生成xml文件（覆盖现有文件）并提交它们。
我们只想提交实际更改的内容，以保持历史记录的清洁。
Our concrete use case:
We nightly run a script that generates xml files (overwriting existing files) and commits them.
We would like to commit only the ones that actually changed to keep the history clean.
预先感谢！
1月
Thanks in advance!
Jan
推荐答案
在实际执行文件检入时，请查看在历史记录视图中实际创建的变更集。通常，TFS将检查上载的文件的内容，并且仅在文件的MD5哈希与版本控制中使用的最后一个版本不同时，才会在变更集中包含文件。
When you actually perform the check-in of the file, have a look at the changeset that actually is created in the history view. Normally TFS will check the contents of the files uploaded and will only include a file in the changeset if the MD5 hash of the file is different to the last version that was in version control.
这不是您看到的内容吗？您是否具有相同内容的多个版本的同一文件？如果是这样-文件具有什么扩展名？ .XML还是其他？
Is this not what you see? Do you have multiple versions of the same file that are identical in content? If so - what extension do the files have? .XML or something else?
这篇关于TFS提交未更改的文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
