在电子邮件上迷路了吗? [英] Git over Email?

查看:100
本文介绍了在电子邮件上迷路了吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

假设没有中心服务器的网络访问是零星的,那么使用git保持三个或更多分支同步的最佳方法是什么?有没有办法只提取我的增量,通过电子邮件发送这些增量,然后将其合并到另一端?

Assuming network access is sporadic with no central server, what would be the best way to use git to keep three or more branches in sync? Is there a way to extract just my deltas, email those, and merge them on the other end?

推荐答案

虽然"git format-patch"和"git am"是管理来自非git源的补丁的好方法,但对于git存储库,您应该调查"git bundle" .

While "git format-patch" and "git am" are great ways to manage patches from non-git sources, for git repositories you should investigate "git bundle".

"git bundle"以及子命令"create"和"unbundle"可用于创建和使用增量提交的二进制blob,可用于通过备用文件传输机制跨弱"链接传输分支历史记录(例如电子邮件,蜗牛邮件等).

"git bundle" and the subcommands "create" and "unbundle" can be used to create and use a binary blob of incremental commits that can be used to transfer branch history across a 'weak' link via an alternative file transfer mechanism (e.g. email, snail-mail, etc.).

git捆绑包将保留提交ID,而format-patch/am不会导致目标提交不相同(不同的SHA1).

git bundles will preserve commit ids, whereas format-patch/am will not resulting in the destination commits not being identical (different SHA1s).

这篇关于在电子邮件上迷路了吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆