Skip to content

Possible bug fix for memory region enumeration #101

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

Merged
merged 1 commit into from
Apr 5, 2019

Conversation

Rob--
Copy link
Contributor

@Rob-- Rob-- commented Apr 4, 2019

Not familiar with the code base at all, but I was reading through this file and it seems as though there is a possible typo? I'm not sure if the original behaviour was intended or not but I thought it was worth pointing this out in case it was an accident!

Not familiar with the code base at all, but I was reading through this file and it seems as though there is a possible typo? I'm not sure if the original behaviour was intended or not but I thought it was worth pointing this out in case it was an accident!
@KN4CK3R
Copy link
Member

KN4CK3R commented Apr 5, 2019

This looks like a copy paste error. Thank you for the fix.

@KN4CK3R KN4CK3R merged commit 4dd5ff6 into ReClassNET:master Apr 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants