On Git's lack of respect for immutability and the Best Practices for a DVCS
february 2009 by uggedal
I think "git add --p" is "really cool", but it doesn't qualify as a "best practice". It allows the developer to commit code they have never seen. Yes, that commit happens in a private instance of the repo, but that code is eligible to be pushed into another instance.
git
usability
dvcs
continuos
integration
breakage
immutabilitty
february 2009 by uggedal
related tags
abstraction ⊕ analysis ⊕ app ⊕ apt ⊕ backup ⊕ bazaar ⊕ branch ⊕ branches ⊕ branching ⊕ breakage ⊕ bridge ⊕ browser ⊕ bug ⊕ bugtracking ⊕ bzr ⊕ camp ⊕ cherrypicking ⊕ code ⊕ community ⊕ comparison ⊕ config ⊕ configuration ⊕ continuos ⊕ corporate ⊕ darcs ⊕ database ⊕ dependencies ⊕ deployment ⊕ development ⊕ distributed ⊕ distutils ⊕ django ⊕ dscm ⊕ dump ⊕ dvcs ⊖ education ⊕ etc ⊕ fork ⊕ gateway ⊕ gem ⊕ git ⊕ http ⊕ immutabilitty ⊕ insecurity ⊕ integration ⊕ issuetracker ⊕ learning ⊕ legacy ⊕ library ⊕ lightweight ⊕ manual ⊕ mecurial ⊕ mercurial ⊕ merging ⊕ opensource ⊕ packaging ⊕ pacman ⊕ patch ⊕ pip ⊕ plaintext ⊕ programming ⊕ proxy ⊕ puppet ⊕ python ⊕ reference ⊕ release ⊕ religius ⊕ repository ⊕ scm ⊕ sftp ⊕ sharing ⊕ social ⊕ subversion ⊕ svn ⊕ testing ⊕ theory ⊕ topicbranch ⊕ transparent ⊕ unix ⊕ unsafe ⊕ usability ⊕ vcs ⊕ war ⊕ work ⊕ workflow ⊕Copy this bookmark: