Submitting patches.

[slembcke]

If you want to submit a patch to Chipmunk, it saves me a great deal of time and energy if you send me a pull request on GitHub. Sending a zip file of the modified source or a hand typed list of changes can be very tedious to integrate. A lot of times when given a patch of this form I won't have the time to look at it right away and I end up forgetting entirely. Given a proper patch file, I can apply the patch in a second or two and then easily browse the changes made to see what you changed.

Probably the best place to learn about Git is GitHub. They have a lot of walkthroughs that are better than anything I could write:
https://github.com

Chipmunk's GitHub page:
https://github.com/slembcke/Chipmunk-Physics

[supertommy]

FYI: I had to remove the 's' from https in the svn checkout command line, or googlecode would insist on a username and password.

[slembcke]

Ah yes. Good catch. The http url is read-only, but does not require authentication.

[blachman]

[PeskyJ]

I submitted a patch to the issue tracker... how do you change the type from "defect" in that thing?

Anyhow, hope that's the right place, if not let me know and I can re-post here as an attachment or email or whatever.

J

[slembcke]

I did not realize that they added an issue tracker to google projects... (or maybe I just never noticed it existed at all). Shame it doesn't notify you by email or something when an issue is submitted.

I'll take a look at it.

[viblo]

Its been there for a very long time
If you go to the issues admin part you can set an email adr that will get a notification each time an issue is created/updated
(for pymunk this is located at http://code.google.com/p/pymunk/adminIssues )

[jeapostrophe]

I sent you a patch.

[Beoran]

Here's a patch for issue 35 I reported. I tested it and it solves the problem I discovered in with the chipmunk ruby bindings.

[slembcke]

Woo. This was *waaay* out of date. I guess people already know to look at Github.