我对任何 dvcs 上的 wiki 的主要抱怨是合并， 因为在编辑 wiki 时根据页面进行工作确实很有意义， 然而，所有 dvc 都是基于文件树
，bzr 的基于暴露目录的樱桃采摘并不正确 （主要是为后面的合并冲突做基础）
i implemented a simple wiki on top of mercurial
my main gripe with wikis on any dvcs is merging, as it indeed makes much sense to work in terms of pages when editing a wiki, however all dvcs's are based on trees of files
btw, bzr's exposed directory based cherry picking doesn't get that right (it mainly makes up the base for merge conflicts later)
I use mercurial for incremental backups to non-mercurial aware online file storage. Just have a repo that contains what's already backed up, and hg bundle against it. Then push. Copy the bundle to a live mesh synced folder and presto, automatic backup and distribution to all my machines. (Note: encrypt the bundle first - I trust no one to respect my privacy). Of course, full backup is just as easy with hg bundle -all.
Although I prefer Mercurial to git, I like Gist snippet service of the github.com. It's a paste site on steroids - allows to version snippets, access private snippets via SSL, and more.
And there's always fossil, which is a DVCS with both bug tracking and wiki built in. Made by the creator of sqlite, and uses an sqlite database as its repository.
发布评论
评论（5）
我在 Mercurial 之上实现了一个简单的 wiki，
我对任何 dvcs 上的 wiki 的主要抱怨是合并，
因为在编辑 wiki 时根据页面进行工作确实很有意义，
然而，所有 dvc 都是基于文件树
，bzr 的基于暴露目录的樱桃采摘并不正确
（主要是为后面的合并冲突做基础）
i implemented a simple wiki on top of mercurial
my main gripe with wikis on any dvcs is merging,
as it indeed makes much sense to work in terms of pages when editing a wiki,
however all dvcs's are based on trees of files
btw, bzr's exposed directory based cherry picking doesn't get that right
(it mainly makes up the base for merge conflicts later)
我使用 Mercurial 对非 Mercurial 感知的在线文件存储进行增量备份。 只需拥有一个包含已备份内容的存储库，并对其进行 hg 捆绑即可。 然后推。 将捆绑包复制到实时网格同步文件夹，然后自动备份并分发到我的所有计算机。 （注意：首先对捆绑包进行加密 - 我相信没有人会尊重我的隐私）。 当然，使用
hg bundle -all进行完整备份同样简单。I use mercurial for incremental backups to non-mercurial aware online file storage. Just have a repo that contains what's already backed up, and hg bundle against it. Then push. Copy the bundle to a live mesh synced folder and presto, automatic backup and distribution to all my machines. (Note: encrypt the bundle first - I trust no one to respect my privacy). Of course, full backup is just as easy with
hg bundle -all.虽然我更喜欢 Mercurial 而不是 git，但我喜欢 github.com 的 Gist 片段服务。 它是一个强大的粘贴网站 - 允许对代码片段进行版本控制、通过 SSL 访问私有代码片段等等。
Although I prefer Mercurial to git, I like Gist snippet service of the github.com. It's a paste site on steroids - allows to version snippets, access private snippets via SSL, and more.
不是我自己的项目，只是遇到了几个使用 git 的分布式问题跟踪系统：
git 问题
ticgit
而且总是有fossil，这是一个内置了错误跟踪和 wiki 的 DVCS。由 sqlite 的创建者制作，并使用 sqlite 数据库作为其存储库。
Not my own projects, but just came across a couple of distributed issue tracking systems that use git:
git-issues
ticgit
And there's always fossil, which is a DVCS with both bug tracking and wiki built in. Made by the creator of sqlite, and uses an sqlite database as its repository.
DVCS 是分布式文件系统的基础。
DVCS is the underpinning of distributed filesystems.