4 ms·

If the concern is the computer failing, you should do backups. And it's probably simpler to use automated backups than using git push as a backup mechanism.

by Dewie 12y ago

maguirre 12y ago
Automated backups are useful. However how often can you backup? If you are hacking/experimenting backing up after every change seems too resource intensive
- Dewie 12y ago
  I back up every 10 minutes. So I lose 10 minutes if I screw something up, which is acceptable to me. I guess I could back up every 5 minutes, and I don't think that would be a problem.
Touche 12y ago
Adding another thing I have to keep track of and maintain is not simpler than 1 command that is pure muscle reflex.
- Dewie 12y ago
  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'?
  - Anderkent 12y ago
    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)
    - Dewie 12y ago
      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?
      - Touche 12y ago
        All to avoid typing git push? Why?
        Dewie 12y ago
        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.

If the concern is the computer failing, you should do backups. And it's probably simpler to use automated backups than using git push as a backup mechanism.

by Dewie 12y ago

If the concern is the computer failing, you should do backups. And it's probably simpler to use automated backups than using git push as a backup mechanism.

maguirre 12y ago

Automated backups are useful. However how often can you backup? If you are hacking/experimenting backing up after every change seems too resource intensive

Dewie 12y ago
I back up every 10 minutes. So I lose 10 minutes if I screw something up, which is acceptable to me. I guess I could back up every 5 minutes, and I don't think that would be a problem.

Touche 12y ago

Adding another thing I have to keep track of and maintain is not simpler than 1 command that is pure muscle reflex.

Dewie 12y ago
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'?
- Anderkent 12y ago
  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)
  - Dewie 12y ago
    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?
    - Touche 12y ago
      All to avoid typing git push? Why?
      - Dewie 12y ago
        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.