diff options
| author |  mark@6b90344cdab3158eacb94a3944460d138afc9bef <mark@web> | 2016-02-02 18:28:44 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-02-02 18:28:44 +0000 |
| commit | 752859b3b927a507e3817532d7783e8c872453a5 (patch) | |
| tree | 4ccbc2909ae70c91b94c335f90719e977fdd8c57 /doc | |
| parent | af44484d2f0f5c4c6543d30c96dc1a7e15155f68 (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/Multisession_compatible__63__.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/Multisession_compatible__63__.mdwn b/doc/forum/Multisession_compatible__63__.mdwn new file mode 100644 index 000000000..6c117a5ba --- /dev/null +++ b/doc/forum/Multisession_compatible__63__.mdwn @@ -0,0 +1,8 @@ +Thanks for the great tool! + +Is git-annex multisession compatible? I'm assuming that an "add" for example, will switch to the git-annex branch, commit data, and switch back to the previous branch. Is this protected by a Lock of some sort so that if two separate processes are interacting with the same repo/annex simultaneously there won't be any corruption? + +If not, is this something I could add within my python class that is implementing the interface to the Annex? + +Thanks, +Mark |