4 ms·

>I'm used git for small, personal collaborations This is a great reason to use email! You don't need a platform at all, you can use the tools presented in this

>I'm used git for small, personal collaborations This is a great reason to use email! You don't need a platform at all, you can use the tools presented in this tutorial to email your work directly to your collaborators. Outside of that, email is used for collaboration with many large and important projects, such as Linux, PostgreSQL, and git itself. I have some writings about why I think this workflow is nice: https://drewdevault.com/2018/07/23/Git-is-already-distributed.html https://drewdevault.com/2018/07/23/Git-is-already-distribute... https://drewdevault.com/2018/07/02/Email-driven-git.html https://drewdevault.com/2018/07/02/Email-driven-git.html (forgive the formatting on the latter, fix is being deployed now)

bo1024 8y ago
Thanks for the reply. I'll explain why I'm still confused/unsure what is going on, hope it is useful feedback. My understanding of git is that there is a server, and users push/pull to the server. So from an initial look at everything you provided, it sounded to me like git-send-email gives people email notifications to know what has been changed on the server, for example. I don't know what "email-driven workflow" means and that was my best guess. But from someone else's reply, it sounds like you are discussing an alternative to the server model, where there is no server at all and pushes and pulls are communicated completely via email. This seems consistent with your 2018-07-02 post, but honestly I didn't really get it from there the first time. Is it correct?
- Sir_Cmpwn 8y ago
  That's right. git stores all of the data that could be on the server on your local machine. Every clone of a git repository contains the full history of that repo. git send-email allows you to send commits to other people over email.
  - bo1024 8y ago
    Okay, thanks! I am finally getting it.
- rgoulter 8y ago
  > My understanding of git is that there is a server, and users push/pull to the server. Git is a distributed VCS and so doesn't need a (centralised) server to share code. Sites like GitHub, GitLab or SourceHut let you host a git repository that you can push/pull from. It's a convenient way of sharing code, and collaborating with others. But you can also apply changes to a repo using patches prepared by email. > ....where there is no server at all and pushes and pulls are communicated completely via email. I'd emphasise that changes to a repo can come from diffs or patches as well, not just pushes/pulls from another repository. FWIW, Git book has details about how one might make use of patches received by email. https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_patches_from_email https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a... https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Email https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Em...

bo1024 8y ago

Thanks for the reply. I'll explain why I'm still confused/unsure what is going on, hope it is useful feedback. My understanding of git is that there is a server, and users push/pull to the server. So from an initial look at everything you provided, it sounded to me like git-send-email gives people email notifications to know what has been changed on the server, for example. I don't know what "email-driven workflow" means and that was my best guess. But from someone else's reply, it sounds like you are discussing an alternative to the server model, where there is no server at all and pushes and pulls are communicated completely via email. This seems consistent with your 2018-07-02 post, but honestly I didn't really get it from there the first time. Is it correct?

Sir_Cmpwn 8y ago
That's right. git stores all of the data that could be on the server on your local machine. Every clone of a git repository contains the full history of that repo. git send-email allows you to send commits to other people over email.
- bo1024 8y ago
  Okay, thanks! I am finally getting it.
rgoulter 8y ago
> My understanding of git is that there is a server, and users push/pull to the server. Git is a distributed VCS and so doesn't need a (centralised) server to share code. Sites like GitHub, GitLab or SourceHut let you host a git repository that you can push/pull from. It's a convenient way of sharing code, and collaborating with others. But you can also apply changes to a repo using patches prepared by email. > ....where there is no server at all and pushes and pulls are communicated completely via email. I'd emphasise that changes to a repo can come from diffs or patches as well, not just pushes/pulls from another repository. FWIW, Git book has details about how one might make use of patches received by email. https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_patches_from_email https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a... https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Email https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Em...