diff options
| author |  olaf <olaf@web> | 2017-08-15 23:42:07 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-08-15 23:42:07 +0000 |
| commit | 6505cb5116223071aa8ee782a7987932a010e36a (patch) | |
| tree | 7a3a65a0b3a0e7ae0d1673ba6ecfe2c04cd08823 | |
| parent | 5e27be757a375ceafff474d32f38824bbeb3a510 (diff) | |
| -rw-r--r-- | doc/forum/Assistant_-_pausing___47___using_lock_file_to_get_atomic__40__ish__41___states__63__.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/Assistant_-_pausing___47___using_lock_file_to_get_atomic__40__ish__41___states__63__.mdwn b/doc/forum/Assistant_-_pausing___47___using_lock_file_to_get_atomic__40__ish__41___states__63__.mdwn new file mode 100644 index 000000000..b75a6eb27 --- /dev/null +++ b/doc/forum/Assistant_-_pausing___47___using_lock_file_to_get_atomic__40__ish__41___states__63__.mdwn @@ -0,0 +1,10 @@ +Is there functionality to pause the assistant so that a group of changes all get committed at once? + +The case I'm thinking of is using git-annex to manage distribution of my bup backups. I want to make sure that all the backup files are written - and then the par2 files generated from `fsck`ing - before they are committed and shipped. + +Naively, I'm looking for something as simple as a lockfile to touch at the start of the backup and then remove afterwards. + +Of course I could just run `git annex sync --content` after the backup is run, but, I'm was thinking that the assistant might be more set and forget... + + +Does anyone do pausing or something similar? |