With GitHub, you don't have to make patches anymore. The process morphs to look something like this:
1) You make your changes in your local repo on your hack or whatever environment you use. You use a separate branch for each bug/feature you're working on.
2) When you're ready to submit, you push your changes up to your forked repository on GitHub. This is done with git push with some arguments and is really easy.
3) On GitHub's web site, you submit a pull request to the main Dreamwidth repository.
4) Admins can then review your pull request and request changes and/or merge it in to the base repo.
5) You close out your branches. Or keep them open if you want to do more work on this feature/bug -- you can submit another pull request later!
For more information on pull requests, and why they're so awesome:
They really are amazing. You can upload code, discuss it, upload more code, preview things, bounce it back and forth, and eventually merge it in when it's ready to go. It's brilliant.
I wrote up a thing on how to use git flow with GitHub here:
It's pretty easy. There is no "create a patch" and upload files. You make your changes in a branch, commit them, and create a pull request. It's pretty easy.
no subject
1) You make your changes in your local repo on your hack or whatever environment you use. You use a separate branch for each bug/feature you're working on.
2) When you're ready to submit, you push your changes up to your forked repository on GitHub. This is done with git push with some arguments and is really easy.
3) On GitHub's web site, you submit a pull request to the main Dreamwidth repository.
4) Admins can then review your pull request and request changes and/or merge it in to the base repo.
5) You close out your branches. Or keep them open if you want to do more work on this feature/bug -- you can submit another pull request later!
For more information on pull requests, and why they're so awesome:
http://help.github.com/send-pull-requests/
They really are amazing. You can upload code, discuss it, upload more code, preview things, bounce it back and forth, and eventually merge it in when it's ready to go. It's brilliant.
I wrote up a thing on how to use git flow with GitHub here:
http://qq.is/article/git-flow-on-github
It's pretty easy. There is no "create a patch" and upload files. You make your changes in a branch, commit them, and create a pull request. It's pretty easy.