Skip to content
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

Close this issues page, point to Metasploit-Framework's issues #35

Open
todb-r7 opened this issue Apr 2, 2015 · 2 comments
Open

Close this issues page, point to Metasploit-Framework's issues #35

todb-r7 opened this issue Apr 2, 2015 · 2 comments
Labels

Comments

@todb-r7
Copy link

todb-r7 commented Apr 2, 2015

Since 614b0aa in 2011, we've seen one issue filed against this repo.

I suspect that there is no case anyone would want to file a bug here -- they really want to file a bug over on rapid7/metasploit-framework.

Seems like the CONTRIBUTING.md page should point people there, and disable issues.

I bet this goes for a few of the support gems. I'm happy to sort this out. About the only support gem that gets issues with any frequency is rapid7/meterpreter.

@todb-r7
Copy link
Author

todb-r7 commented Apr 2, 2015

Assigned as a "question" to @trosen-r7.

@jhart-r7
Copy link
Contributor

jhart-r7 commented Dec 8, 2015

I guess the only time submitting an issue here would ever make sense is if the use-case in question was using metasploit-model in something other than metasploit-framework or pro, but that may never happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants