![jh@sigmoid.social (Mastodon) on Twitter: "The reason git breaks @ProjectJupyter stems from an incompatibility between the format Jupyter notebooks use (JSON) and the format that git conflict markers assume. git merges create invalid jh@sigmoid.social (Mastodon) on Twitter: "The reason git breaks @ProjectJupyter stems from an incompatibility between the format Jupyter notebooks use (JSON) and the format that git conflict markers assume. git merges create invalid](https://pbs.twimg.com/media/FbC2zCiakAIbaBk.png)
jh@sigmoid.social (Mastodon) on Twitter: "The reason git breaks @ProjectJupyter stems from an incompatibility between the format Jupyter notebooks use (JSON) and the format that git conflict markers assume. git merges create invalid
![Jakub Kozłowski @kubukoz@mstdn.party on Twitter: "I'm pleased to announce that git conflict markers are parsed as valid Scala. https://t.co/s7RGqTTAar" / Twitter Jakub Kozłowski @kubukoz@mstdn.party on Twitter: "I'm pleased to announce that git conflict markers are parsed as valid Scala. https://t.co/s7RGqTTAar" / Twitter](https://pbs.twimg.com/media/FhFMLYdXEAAtKqO.jpg:large)
Jakub Kozłowski @kubukoz@mstdn.party on Twitter: "I'm pleased to announce that git conflict markers are parsed as valid Scala. https://t.co/s7RGqTTAar" / Twitter
![It's not possible to merge conflicts in the same branch. · Issue #11 · samoshkin/vim-mergetool · GitHub It's not possible to merge conflicts in the same branch. · Issue #11 · samoshkin/vim-mergetool · GitHub](https://user-images.githubusercontent.com/6280763/66709522-c66e3a00-ed2b-11e9-95d0-be33a50112f5.png)