4 ms·

- GitHub + why do we centralize issues, documents for a distributed version control? + why do we use a a closed source, walled garden to develop free softw

- GitHub + why do we centralize issues, documents for a distributed version control? + why do we use a a closed source, walled garden to develop free software? - Git + it's a leaky abstraction. + why do we need to know about the stash? + why is it that changing to a different branch doesn't give any visual clue, even worst it keeps the files I'm working on that are not part of the repository yet. for an academic treatment of the defects in Git read: What's Wrong with Git? A Conceptual Design Analysis S. Perez De Rosso and D. Jackson. In Proceedings of the 2013 ACM International Symposium on New Ideas, New Paradigms, and Reflections on Programming & Software (Onward! 2013)

recursive 6y ago
99% of git usage seems to involve one or fewer remotes. Maybe multiple remotes is just not that useful.
- zenhack 6y ago
  Fwiw, my usual work flow involves 2 remotes, one for the project's mainline repo and one for my fork.
  - ufmace 6y ago
    I frequently have 3+. Github/Bitbucket if it's shared there, maybe a original repo if it's a fork I'm submitting PRs too. My server if it's something I'm running an instance of - I like to deploy my personal services via Git pushes. Sometimes a copy of the same codebase on another personal computer or two - if I don't feel like pushing it to Github, sometimes I'll push and pull between computers directly.
karlicoss 6y ago
- 100% agree about github issues! Not just from the walled garden perspective, but also because you can't quickly grep over all bugs as you can over the code. git-bug seems to be a good step towards this https://github.com/MichaelMure/git-bug#readme https://github.com/MichaelMure/git-bug#readme - for git stash: there is a config setting https://cscheng.info/2017/01/26/git-tip-autostash-with-git-pull-rebase.html https://cscheng.info/2017/01/26/git-tip-autostash-with-git-p... Arguably should be a default, but then when it fails, new git users would end up even more confused about what happened...

recursive 6y ago

99% of git usage seems to involve one or fewer remotes. Maybe multiple remotes is just not that useful.

zenhack 6y ago
Fwiw, my usual work flow involves 2 remotes, one for the project's mainline repo and one for my fork.
- ufmace 6y ago
  I frequently have 3+. Github/Bitbucket if it's shared there, maybe a original repo if it's a fork I'm submitting PRs too. My server if it's something I'm running an instance of - I like to deploy my personal services via Git pushes. Sometimes a copy of the same codebase on another personal computer or two - if I don't feel like pushing it to Github, sometimes I'll push and pull between computers directly.

karlicoss 6y ago

- 100% agree about github issues! Not just from the walled garden perspective, but also because you can't quickly grep over all bugs as you can over the code. git-bug seems to be a good step towards this https://github.com/MichaelMure/git-bug#readme https://github.com/MichaelMure/git-bug#readme - for git stash: there is a config setting https://cscheng.info/2017/01/26/git-tip-autostash-with-git-pull-rebase.html https://cscheng.info/2017/01/26/git-tip-autostash-with-git-p... Arguably should be a default, but then when it fails, new git users would end up even more confused about what happened...