Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2020-04-08 14:12:20 -04:00
commit aba905152a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 44 additions and 0 deletions

View file

@ -0,0 +1,34 @@
### Please describe the problem.
### What steps will reproduce the problem?
```
chymera@silenthost /mnt/data/ni_data $ git annex direct
[...]
direct ofM.vta/20180730_070313_6592_1_1/8/pdata/1/reco ok
direct ofM.vta/20180730_070313_6592_1_1/8/pdata/1/visu_pars ok
direct ofM.vta/20180730_070313_6592_1_1/8/pulseprogram ok
direct ofM.vta/20180730_070313_6592_1_1/8/specpar ok
direct ofM.vta/20180730_070313_6592_1_1/8/uxnmr.info ok
error: git-annex died of signal 11
chymera@silenthost /mnt/data/ni_data $ git annex direct
commit
^C
```
I let it try to resume for a very long time (about a day) and it did nothing.
### What version of git-annex are you using? On what operating system?
6.20170818 on Gentoo Linux
### Please provide any additional information below.
This is a fairly large repository which was only just cloned and with all data transferred (`git clone` and `git annex get .` worked fine).

View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="comment 5"
date="2020-04-08T01:08:10Z"
content="""
> Surely values that git does not even document can be considered to have undefined behavior.
yeah. integers which aren't 0 or 1 are indeed a dark (undocumented) zone. Might be worth contributing to git and making them documented (probably better to not change behavior at this point).
"""]]