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

A question about the Issue tracker. #4

Closed
wants to merge 1 commit into from
Closed

A question about the Issue tracker. #4

wants to merge 1 commit into from

Conversation

arbox
Copy link
Contributor

@arbox arbox commented Feb 17, 2017

This is merely not a pull request but a question, since the README points for issue tracking to this repository. And the repository has no issues enabled.
The question is: Where is the right place to work with Tcl/Tk issues?

This is merely not a pull request but a question, since the README points for issue tracking to this repository. And the repository has no issues enabled.
The question is: Where is the right place to work with Tcl/Tk issues?
@basex
Copy link

basex commented Feb 28, 2017

I'm not a maintainer, but I think it's on the Ruby Issue Tracker: https://bugs.ruby-lang.org/projects/ruby-trunk/issues

@arbox
Copy link
Contributor Author

arbox commented Mar 1, 2017

I'm asking that here since many issues have been moved from the Ruby Trunk. Tk does not belong to the Ruby stdlib any more, it's a separate library packaged as a gem.

@hsbt
Copy link
Member

hsbt commented Mar 1, 2017

This is a canonical place to report the issue of tk gem. We have no resource to handle only issue report. Therefore we open only pull request also report with patch or reproduction code like a test.

@arbox
Copy link
Contributor Author

arbox commented Mar 1, 2017

@hsbt Ok, that clarifies the state of affairs :) I'll formulate a note for the projects readme about this point as a new pull request. Thank you!

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

Successfully merging this pull request may close these issues.

3 participants