Timeline for Business case for decentralized version control systems
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2011 at 2:50 | comment | added | Benbob | Thanks for the clarification. Git wasn't exactly easy for me coming from subversion. A lot of the commands have the same word but do different things. | |
| May 21, 2011 at 14:19 | comment | added | Karl Bielefeldt | @Keyo, I chose bzr because I had to teach DVCS to myself and bzr is the most newbie-friendly. I have switched to git for speed, features, and stability since then. Bazaar also hashes its revisions and has globally unique identifiers, they just aren't the default exposed to the user. Their revision numbers are really no different than using HEAD~1, HEAD~2, etc. in git. It's very rare you need the actual hash, but it's the first thing you learn in git and is always in your face. Hiding that from the user unless you really need it is one reason bzr is more newbie friendly. | |
| May 21, 2011 at 14:02 | history | edited | user1249 | CC BY-SA 3.0 | "here" sucks. |
| May 21, 2011 at 13:12 | comment | added | Benbob | Your blog entries are well written. I haven't yet read all of them though. I wonder why you have chosen Bzr when Git and Hg seem to be far more popular. People seem to hate Bzr for being slow. I'm also a fan of Git because of the tree hashes instead of revision numbers, which seems very secure to me. Won't the bzr rev numbers get all scrambled up when branches are merged? | |
| Feb 26, 2011 at 22:37 | history | answered | Karl Bielefeldt | CC BY-SA 2.5 |