mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

close too old version

Browse source
This commit is contained in:
Joey Hess 2020-05-04 13:05:41 -04:00
parent f9ed30de3b
commit 3e91461c0f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 14 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume.mdwn
View file

@ -29,6 +29,4 @@ I let it try to resume for a very long time (about a day) and it did nothing.
This is a fairly large repository which was only just cloned and with all data transferred (`git clone` and `git annex get .` worked fine). This is a fairly large repository which was only just cloned and with all data transferred (`git clone` and `git annex get .` worked fine).
> [[closing|done]] per my comment --[[Joey]]

13
doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume/comment_1_2aa8d50cef4f85d958371e2177f87d3a._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-05-04T17:01:56Z"
content="""
git-annex no longer supports direct mode in current versions,
so whatever code might have caused that behavior is removed.
The signal 11 is, however, suprising. If a current version of git-annex
segfaults, it would be worth filing a bug report and chasing that down,
although only after you test your machine's memory for problems that might
lead to a sefault.
"""]]