Thanks to visit codestin.com
Credit goes to github.com

Skip to content

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

Merged
merged 12 commits into from
Oct 25, 2011
Merged

Merge v1.1.x #538

merged 12 commits into from
Oct 25, 2011

Conversation

jdh2358
Copy link
Collaborator

@jdh2358 jdh2358 commented Oct 18, 2011

merge bugfixes from v1.1.x

@mdboom
Copy link
Member

mdboom commented Oct 21, 2011

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?

@ivanov
Copy link
Member

ivanov commented Oct 22, 2011

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

@jdh2358
Copy link
Collaborator Author

jdh2358 commented Oct 25, 2011

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.

jdh2358 added a commit that referenced this pull request Oct 25, 2011
@jdh2358 jdh2358 merged commit b269839 into matplotlib:master Oct 25, 2011
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.

5 participants