bitbucket：分叉与克隆？
将 Mercurial 与托管在 bitbucket 上的私有存储库结合使用。我需要向应用程序添加一些新功能，这可能最终会带来重大变化。我一直在争论创建命名分支还是克隆存储库。我认为克隆对我的案例更有意义，因为它几乎是一个新项目，将大量借鉴当前项目。
所以我的计划是在 bitbucket 上创建一个全新的存储库，并将我的本地存储库推送到这个新存储库。
现在我继续使用 bitbucket，发现了一个分叉功能。这似乎克隆了存储库服务器端，但也记住了它所分叉的原始存储库，并具有显示它们之间差异的工具。
这样做的优点/缺点是什么？我应该只使用叉子还是有什么问题？
Using Mercurial with a private repository hosted at bitbucket. I need to add some new features to an application that will potentially end up being serious changes. I've been debating between creating a named branch or cloning the repository. I think cloning makes a little more sense for my case as it's almost a new project that will borrow heavily from the current one.
So my plan was to create a brand new repository on bitbucket and the push my local repository to this new repository.
Now I go on bitbucket and I noticed a fork feature. This seems to clone the repository server side, but also remembers the original repository it was forked from and has tools for showing the difference between them.
What are the pros/cons for this? Should I just use fork or is there any catch?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
没有任何问题。分叉只是普通的克隆。
有时我会先从 Bitbucket 克隆一个项目来使用和研究。当我有补丁时，我会将其分叉到 bitbucket 上，推送到我的新分叉并执行拉取请求。
所以这意味着你现在不必分叉它。只需在本地克隆它，稍后再决定是否要在 Bitbucket 上分叉。
There are no catches. Forks are just regular clones.
Sometimes I first clone a project from Bitbucket to use and study. And when I have a patch I fork it on bitbucket, push to my new fork and do a pull-request.
So this means you don't have to fork it now. Just clone it locally and decide later that you may want to fork on Bitbucket.