您可以使用环形拓扑设置 Git 源代码控制吗?
我想知道是否有人设置过具有环形拓扑的 Git 源代码控制系统 (http://en .wikipedia.org/wiki/Ring_topology)。我认为这应该可行,但我想知道是否有人验证过。
假设我有一家小公司,有 4 名远程开发人员:Alex、Bob、Carrie 和 Dan
假设团队的每个成员都有一个 Git 存储库,我们将其设置为
Alex 存储库,并将原点设置为 Bob
Bob 存储库,原点设置为 Carrie
Carrie 存储库,原点设置为 Dan
Dan 存储库,原点设置为 Alex
由于所有提交均由 SHA1 哈希跟踪,因此当事情返回环时,似乎应该不会出现任何问题。
只是想知道是否有人测试过或有过此类设置的经验?
I was wondering if anyone has ever set up a Git source control system with a ring topology (http://en.wikipedia.org/wiki/Ring_topology). I think this should work, but I was wondering if anyone has verified it.
Say I have a small company with 4 remote developers: Alex, Bob, Carrie, and Dan
Assume that each member of the team has a Git repository which we will be setup as
Alex repository with origin set to
BobBob repository with origin set to
CarrieCarrie repository with origin set to
DanDan repository with origin set to Alex
Since all commits are tracked by SHA1 hash, it seems that there should be no issues when things come back round the ring.
Just wondering if anyone has tested or experience with this type of setup?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
它应该可以工作,但是(环)更适合环境工作流程。
例如,人们可以想象(不是一个理想的工作流程,但对于这个例子来说它会这样做):
在开发人员中,拓扑更加松散(不一定是环,而是更多的临时网络,具体取决于所需的协作级别)。
It should work, but that (ring) is more suited for environment workflow.
For instance, one could imagine (not an ideal workflow, but for this example it will do):
Amongst developer, the topology is much more loose (not necessarily a ring, but more of an ad-hoc network depending on the collaboration level needed).