git send-emailcommand. I'm going to walk you through using it, but you'll have to learn how to set it up for your smtp server on your own (one hint: if you don't provide an smtp pass as an argument or as a config option you will be prompted for it).
now you have a patch that you haven't pushed yet. you can run one of the following sets of steps to get going.
git format-patch -M HEAD~1 # commitish. commit before the number of patches you want to generate vi 0001-patch-name # and add some description between the --- and the diff stat git send-email 0001-patch-name # can replace this step with MUA of choice
git format-patch -M HEAD~5 # generate a patchset of the last 5 patches git send-email --annotate *patch # will open the core.editor you set in gitconfig to edit the patch
git send-email --annotate --format-patch -M --to=destination-email origin/master # generate all the patches that aren't committed against origin/master branch in your local branch
for the time being you should probably just send it to one of your own projects on cpan so you can see. If you look at the web interface for the bug you'll notice it's clobbered your formatting, same goes with the email RT sends you... so this is useless right? well... certainly doesn't help... now look at the 'with headers' version. Their are lots of headers here, but all your content is intact. Now download this file (right click save as should do it).
you may now ( you may have to run git reset --hard HEAD^ first to undo you last commit).
git apply downloaded-file.txt
which will only apply the diff no commit log or anything (reset without HEAD^ now).
or you can
git am -i downloaded-file.txt-i is interactive and will allow you to choose whole folders full of mail patches and which to apply.
I think this is a good workflow for 1 off patches. obviously you don't send them to yourself, I'm just trying to show you what it's like to send and receive.