版本控制系统如何恢复修订？

本文介绍了版本控制系统如何恢复修订？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我的问题是在标题比声明更普遍。

我只知道大概的差别是源代码版本控制存储信息。 据我了解这样做维基百科，也是如此github上。

但他们都有能力来显示整个文件特别版本。难道他们逐步从第一个版本恢复到特定的一个？

和另外一个问题。如果他们只存储不同，他们是如何展示他们的用户界面与上下文（前和更改后一点文本）。

编辑： github上存储整个快照，而不是增量

解决方案   

我只知道大概的差别是源代码版本控制存储信息。

由于问题Git对存储内容，而不是差异说明了设计决策，这是不是的完全的是什么混帐做。 它确实已经打包的形式虽然，存储deltaified表单对象，使用二进制增量从LibXDiff库。但是，这主要是用于网络传输。 请参见Is git的二进制差异算法（增量存储）标准化？。 这就是为什么Git是resolving三角洲当你取。

My question is more general than declared in title.

I know that source version control stores information only about differences. As I understand so does Wikipedia, and so does github.

But they all have ability to show whole file with particular revision. Do they incrementally restore it from first revision to specific one?

And another one question. If they store differences only, how they show them in ui with context (little bit text before and after changes).

EDIT: github stores whole snapshots instead of deltas

解决方案

I know that source version control stores information only about differences.

As the question Git design decision on storing content rather than differences illustrates, this isn't exactly what Git does. It does has "packed" format though, to store objects in deltaified form, using binary delta from LibXDiff library. But that mainly is used for network transfer. See "Is the git binary diff algorithm (delta storage) standardized?". That is why git is "resolving delta" when you fetch.