From 323fc8af97c4ab904d575c9b2c4b0f2098f1e30f Mon Sep 17 00:00:00 2001 From: "http://identi.ca/cwebber/" Date: Tue, 27 Nov 2012 18:39:11 +0000 Subject: [PATCH] --- ...nlocked_for_a_bit_while_committing_it_repeatedly__63__.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/forum/The_ability_to_leave_a_file_unlocked_for_a_bit_while_committing_it_repeatedly__63__.mdwn diff --git a/doc/forum/The_ability_to_leave_a_file_unlocked_for_a_bit_while_committing_it_repeatedly__63__.mdwn b/doc/forum/The_ability_to_leave_a_file_unlocked_for_a_bit_while_committing_it_repeatedly__63__.mdwn new file mode 100644 index 0000000000..627e3b7360 --- /dev/null +++ b/doc/forum/The_ability_to_leave_a_file_unlocked_for_a_bit_while_committing_it_repeatedly__63__.mdwn @@ -0,0 +1,3 @@ +Sometimes I'm doing something crazy like working in a large GIMP file, and I just want to be able to keep "committing" the changes to the annex but I hate running into the problem of having to keep unlocking the file over and over again while saving. I guess one solution to this might be to use git-annex assistant? But I'm not sure I really want a daemon running, and I don't want this auto-added... I just want to be able to leave the file unlocked while I'm actively working on it, then eventually say "I'm done with this!" and set it back to a state where it's locked. + +Basically, I hate running into "permission denied" errors all the time when I'm saving! I guess I could do some sort of command where I commit to the annex and then immediately unlock again... is there a better way?