We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
currently trying to datalad ls someone else's repository would start crashing with all the errors to be unable to lock that repository, while git annex info is ran. In recent http://git-annex.branchable.com/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/#comment-04827552f7895ca8557e416e48e173c1 @joeyh implemented a config option to avoid "git-annex merge" being ran in the background, which would provide remedy here. The only question either we should make it a default mode of operation for annex info in case of ls, optional, or automagic (enable if permissions issues reported in the initial attempted git annex info run)
datalad ls
git annex info
annex info
ls
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the problem?
currently trying to
datalad ls
someone else's repository would start crashing with all the errors to be unable to lock that repository, whilegit annex info
is ran.In recent http://git-annex.branchable.com/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/#comment-04827552f7895ca8557e416e48e173c1 @joeyh implemented a config option to avoid "git-annex merge" being ran in the background, which would provide remedy here. The only question either we should make it a default mode of operation for
annex info
in case ofls
, optional, or automagic (enable if permissions issues reported in the initial attemptedgit annex info
run)The text was updated successfully, but these errors were encountered: