-
-
Notifications
You must be signed in to change notification settings - Fork 881
objects with indirect reference (leftover from #9447) #11317
New issue
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
Comments
Not forgotten, but CUB3D put a heroic effort into #9447, and he seems to be taking a well-deserved break! Not many people have what it takes to work on these difficult issues. |
Sorry for the late reply, @n0samu (away from computers for two weeks). Of course, @CUB3D deserves a well deserved break after #9447 (and many kudos). The situation now is that #5492 has been closed and I wondered what would happen with the remaining issues (since it took so much effort to deal only with part of the issues containing objects with indirect reference), Sorry, but after so much time (more than 2 years for the loader [#1561]), it seems that it will take a while for these issues to be fixed. Many thanks for your help. |
I don't think #5492 addressed any of the remaining open issues you mentioned, either |
Ok, we will have to wait until someone can fix these issues. |
Uh oh!
There was an error while loading. Please reload this page.
After #9447 was merged (and #5492 was subsequently closed), remaining issues with objects indirectly referenced are issues #1561, #2181, #4088, #5579, #6370 #6581 and #8213.
Excuse me for insisting on this, but they seem to be forgotten.
Many thanks for your excellent work.
The text was updated successfully, but these errors were encountered: