News for hackers. Stuff that matters.
Re:Y U NO commit?? by Dewie on Monday October 20, 2014 @09:34AM (#8482009)
Once you have automated backup set up, how much work is it to maintain? If you keep your code in a few areas/directories (like for example /home/workspace), it seems like a set-it-and-forget-it thing.

PS: how is a command that demands that you write a commit message really just 'muscle memory'?

Re:Y U NO commit?? by Anderkent on Monday October 20, 2014 @09:54AM (#8482096)
git alias cw commit -a -m 'WIP'

;P

(and before the outrage beings, I always push these to my private fork of the main repo, so it's basically just a way of syncing code between machines. Other ways of achieving this with git seem to be always painful; you can push to another machine but only if you rename branches, which is tedious)

Re:Y U NO commit?? by Dewie on Monday October 20, 2014 @01:03PM (#8483181)
Well now we are up to three, arguably distinct needs:

- version control

- backup

- syncing

Syncing can, like backup, be had with software and services that are dedicated to that end. I just use Dropbox, though I'm not that worried about privacy. I guess something could be built "from scratch" with rsync, if the ready-made alternatives arent satisfactory?

Re:Y U NO commit?? by Touche on Monday October 20, 2014 @01:51PM (#8483473)
All to avoid typing git push? Why?
Re:Y U NO commit?? by Dewie on Monday October 20, 2014 @02:46PM (#8483784)
No. You are assuming that my backup and syncing needs overlap with my git usage, so that all I need to backup or sync is to use git push in my already-existing git directories.

I backup and/or sync things that I don't have under version control (git). I only sync my grocery list, for example, since I don't need a history of the 'evolution' of my grocery list. Actually, I may have it under a backup scheme, but that is only because of other files and directories in that directory that I need to backup, and I've at this point set (and partly forgot) that backup plan.

My /home/Dropbox contains a lot of files that I regularly need, and it seems a bit excessive to put all of that into one, monolithic git repo.