On Jan 28, 2015, at 5:02 PM, Chris Angelico <ros...@gmail.com> wrote:
> On Thu, Jan 29, 2015 at 8:52 AM, Devin Jeanpierre > <jeanpierr...@gmail.com> wrote: >> Git doesn't help if you lose your files in between commits, or if you >> lose the entire directory between pushes. > > So you commit often and push immediately. Solved. > > ChrisA Just to expand on what Chris is saying, learn to use branches. I use git flow ([1][2]), but you don't need it, plain old branches are fine. Then you can have a feature branch like 'Joes_current', or something similar which you and only you push/pull from. Whenever you're done with it, you can merge the changes back into whatever you & your group see as the real branch. That is the model I use at work, and it works fairly well, and its saved me once already when the laptop I was working on decided to die on me. Thanks, Cem Karan [1] http://nvie.com/posts/a-successful-git-branching-model/ [2] https://github.com/nvie/gitflow -- https://mail.python.org/mailman/listinfo/python-list
