-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Merge v1.1.x #538
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
Merge v1.1.x #538
Conversation
… in Firefox. Closes matplotlib#510.
…t_size_bug Backend svg firefox font size bug
Reorder ttconv
Figure animated2
Looks good to me. As a policy question, do we generally want to submit pull requests for these kinds of merges, or just do them? |
i've also been puzzled by trying to figure out why we might possibly not want to merge these changes - as @mdboom mentions, I'd be in favor of just pushing changes like these to the the master branch without a PR |
I have no problem just merging these going forward. I had a few hiccups getting my git/github sea legs under me, and submitted a couple of pull requests which were not correct, so I wanted to get some eyeballs on these to make sure I was doing them right. Going forward, I think I can just merge and push. |
merge bugfixes from v1.1.x