Hacker News new | past | comments | ask | show | jobs | submit login

Never heard of it before, but I'm grateful to hear about it! My projects were always small enough that a traditional version control system wasn't worth the time to set up. Just keep an archive of each day's progress in a folder and call it done.

With my latest project, I'm maintaining multiple splits of the codebase for different platform-specific features, and sharing the code with a team member. I was about to bite the bullet and start installing cvs or git in a VM and going through the learning curve, but this seems right up my alley and the kind of system I'd mesh with well. Thanks!




> My projects were always small enough that a traditional version control system wasn't worth the time to set up

There's no such thing as too small: I use Git for everything, including small scripts I may never use again. The setup is "mkdir fooscript && cd fooscript && git init". Plus using GitLuBucket means free backups.


What is GitLuBucket? Google thinks you meant BitBucket, but it seems to be a very weird typo.


GitHub/GitLab/BitBucket. Sorry it wasn't clear :-)


How is `git init` or `hg init` harder than maintaining different versions of your code in separate folders?


It's usually the extra learning curve to use those commands in the first place, not that they are simple to use.


It's really easy to use and it has builtin help like mercurial. No need to read man pages. We use it for all our projects. I also use it for tracking config changes in /etc.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: