← Back to context Comment by lionkor 8 days ago Git is a decentralized protocol, it's just incomplete IMO 10 comments lionkor Reply pmontra 8 days ago There is git format-patch to create a diff and git send-email [2] to mail it to another developer and git-am [3] to apply the patches from a mailbox.The Linux kernel developers have been using that workflow for a lot of time. Maybe still now.[1] https://git-scm.com/docs/git-format-patch[2] https://git-scm.com/docs/git-send-email[3] https://git-scm.com/docs/git-am lucasoshiro 8 days ago > The Linux kernel developers have been using that workflow for a lot of timeYes, they do. Git itself is also developed that way.Btw, you don't need to use format + send-email, send-email calls format-patch under the hood rightbyte 8 days ago Communication layer agnostic text files is a killer feature of git. What MS is doing with Github is typical EEE. ashwinsundar 8 days ago Git and GitHub are not the same thing. git repos can live independently of GitHubWhat features do you feel like git is missing? lionkor 8 days ago Reviewable merge requests, review comments, etc. lucasoshiro 7 days ago You can propose this to the Git mailing list. I don't think this kind of feature should be respnsibility of Git, however, you can try 2OEH8eoCRo0 8 days ago Git has a protocol called email. immibis 8 days ago Indeed push/pull wasn't even the original design intention of Git. It was a tool for one person to manage trees of emailed patch files. RGBCube 8 days ago Radicle.xyz fixes this with COBs (Collaborative Objects). They're stored inside your git repo as normal objects, and benefit from its p2p mechanism as well. It's the true sovereign forge. lucasoshiro 8 days ago > it's just incompleteWhy?
pmontra 8 days ago There is git format-patch to create a diff and git send-email [2] to mail it to another developer and git-am [3] to apply the patches from a mailbox.The Linux kernel developers have been using that workflow for a lot of time. Maybe still now.[1] https://git-scm.com/docs/git-format-patch[2] https://git-scm.com/docs/git-send-email[3] https://git-scm.com/docs/git-am lucasoshiro 8 days ago > The Linux kernel developers have been using that workflow for a lot of timeYes, they do. Git itself is also developed that way.Btw, you don't need to use format + send-email, send-email calls format-patch under the hood
lucasoshiro 8 days ago > The Linux kernel developers have been using that workflow for a lot of timeYes, they do. Git itself is also developed that way.Btw, you don't need to use format + send-email, send-email calls format-patch under the hood
rightbyte 8 days ago Communication layer agnostic text files is a killer feature of git. What MS is doing with Github is typical EEE.
ashwinsundar 8 days ago Git and GitHub are not the same thing. git repos can live independently of GitHubWhat features do you feel like git is missing? lionkor 8 days ago Reviewable merge requests, review comments, etc. lucasoshiro 7 days ago You can propose this to the Git mailing list. I don't think this kind of feature should be respnsibility of Git, however, you can try
lionkor 8 days ago Reviewable merge requests, review comments, etc. lucasoshiro 7 days ago You can propose this to the Git mailing list. I don't think this kind of feature should be respnsibility of Git, however, you can try
lucasoshiro 7 days ago You can propose this to the Git mailing list. I don't think this kind of feature should be respnsibility of Git, however, you can try
2OEH8eoCRo0 8 days ago Git has a protocol called email. immibis 8 days ago Indeed push/pull wasn't even the original design intention of Git. It was a tool for one person to manage trees of emailed patch files.
immibis 8 days ago Indeed push/pull wasn't even the original design intention of Git. It was a tool for one person to manage trees of emailed patch files.
RGBCube 8 days ago Radicle.xyz fixes this with COBs (Collaborative Objects). They're stored inside your git repo as normal objects, and benefit from its p2p mechanism as well. It's the true sovereign forge.
There is git format-patch to create a diff and git send-email [2] to mail it to another developer and git-am [3] to apply the patches from a mailbox.
The Linux kernel developers have been using that workflow for a lot of time. Maybe still now.
[1] https://git-scm.com/docs/git-format-patch
[2] https://git-scm.com/docs/git-send-email
[3] https://git-scm.com/docs/git-am
> The Linux kernel developers have been using that workflow for a lot of time
Yes, they do. Git itself is also developed that way.
Btw, you don't need to use format + send-email, send-email calls format-patch under the hood
Communication layer agnostic text files is a killer feature of git. What MS is doing with Github is typical EEE.
Git and GitHub are not the same thing. git repos can live independently of GitHub
What features do you feel like git is missing?
Reviewable merge requests, review comments, etc.
You can propose this to the Git mailing list. I don't think this kind of feature should be respnsibility of Git, however, you can try
Git has a protocol called email.
Indeed push/pull wasn't even the original design intention of Git. It was a tool for one person to manage trees of emailed patch files.
Radicle.xyz fixes this with COBs (Collaborative Objects). They're stored inside your git repo as normal objects, and benefit from its p2p mechanism as well. It's the true sovereign forge.
> it's just incomplete
Why?