summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://identi.ca/cwebber/ <cwebber@web>2012-11-27 18:39:11 +0000
committerGravatar admin <admin@branchable.com>2012-11-27 18:39:11 +0000
commit86627a551632bd52538e3739006e789ed485fda6 (patch)
treed10e4d567574faa0167330501cfaced2802d402d
parentf27898b8c9e541625d76acc4eb2e301cedcae0fb (diff)
-rw-r--r--doc/forum/The_ability_to_leave_a_file_unlocked_for_a_bit_while_committing_it_repeatedly__63__.mdwn3
1 files changed, 3 insertions, 0 deletions
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 000000000..627e3b736
--- /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?