版本控制(即 Subversion)是否适用于文档跟踪? [英] Is version control (ie. Subversion) applicable in document tracking?

问题描述

我负责大约 100 多个文档(word 文档，不是源代码)，需要我部门的不同人员进行修改.目前，所有文档都在一个共享文件夹中，它们将在其中检索、修改并保存回文件夹中.

I am in charge of about 100+ documents (word document, not source code) that needs revision by different people in my department. Currently all the documents are in a shared folder where they will retrieve, revise and save back into the folder.

我现在正在做的是在共享文件夹中查找修改日期"，打开最近修改过的文档并使用 MS Word 中的跟踪更改"功能来应用更改.我觉得这有点乏味.

What I am doing now is looking up the "date modified" in the shared folder, opened up recent modified documents and use the "Track Change" function in MS Word to apply the changes. I find this a bit tedious.

那么如果我在版本控制数据库中提交它会更好更容易吗?

So will it be better and easier if I commit this in a version control database?

基本上我想保留不同版本的文件.

Basically I want to keep different version of a file.

<小时>我从答案中学到了什么:

---

What have I learn from answers:

• 使用 Time Machine 保存不同的版本(或 Vista 中的影子副本)

• Use Time Machine to save different version (or Shadow copy in Vista)

文字有区别和二进制文件时使用版本控制应用程序.(我不知道那个)

There is a difference between text and binary documents when you use version control app. (I didn't know that)

Diff 不适用于二进制文件

Diff won't work on binary files

用于修订的通知系统(即电子邮件)很棒

A notification system (ie email) for revision is great

Google 文档修订功能.

Google Docs revision feature.

更新:

我试用了 Google Docs 修订功能，觉得它几乎适合我.只是对过于频繁的版本控制(自动保存)有点恼火.

I played around with Google Docs revision feature and feel that it is almost right for me. Just a bit annoyed with the too frequent versioning (autosaving).

但是对我来说感觉合适的东西并不意味着对我的部门来说感觉合适.他们会同意用 Google 保存所有这些文件吗?

But what feels right for me doesn't mean it feels right for my dept. Will they be okay with saving all these documents with Google?

推荐答案

我想似乎没有人问过的一件事是，您是否有法律要求存储文档的更改历史记录?

I guess one thing that nobody seems to have asked is if you have a legal requirement to store history of changes to the doc's?

您是否做或不做都会对您可以考虑的解决方案产生影响.

Whether you do or don't is going to have an impact on what solutions you can consider.

此外，过期副本的通知机制也很有趣.如果工程师 A 有一份文档的副本，然后工程师 B 对其进行编辑并提交您希望工程师 A 收到其副本已过期的通知.

Also a notification mechanism for out of date copies is also a bundle of fun. If engineer A has a copy of a document and engineer B then edits it and commits the changes you want engineer A to be notified that his copy is out of date.

文档控制很容易成为真正的蠕虫.

Document control can become a real can of worms quite easily.

也许将文档保存在 CVS 或 SVN 下并进行设置，以便在更新同一文档时向签出副本的任何人生成电子邮件.是否已签入存储库?

Maybe keep the doc's under CVS or SVN and set it up so that emails are generated to whoever has checked out a copy when updates for the same doc. are checked in to the repository?

我忘了添加不要忘记使用二进制开关，例如-kb 用于 CVS，在添加新文档时.否则，您将获得与附加了相关配置管理数据的关键字字符串的 ascii 匹配的任何数据序列，从而破坏您的文档.数据.

I forgot to add don't forget to use the binary switch, e.g. -kb for CVS, when adding the new doc. Otherwise, you will get any sequences of data that happen to match the ascii for keyword strings having the relevant config management data appended thereby corrupting your doc. data.

这篇关于版本控制(即 Subversion)是否适用于文档跟踪?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！