How to Patch WordPress
With the looming release of WordPress 2.0, there are a bunch of folks that are submitting bug fixes that say things like, “I would submit this to Trac, but I don’t know how.”
I think even more people are suggesting that writing to the mailing list with their bugs to “confirm” them is better than submitting them directly to Trac. I suppose if you’re not sure something is a bug, it might be worthwhile to ask someone else (I would ask on IRC at #wordpress on irc.freenode.net) but it really is better to have a formal record of an issue, even if it turns out that what you’re experiencing is expected behavior. If you really fear that it’s something to do specifically with your installation, check on IRC or maybe try a fresh install.
Nevertheless, it might be useful to folks to learn how I do it. I’m not saying my method is correct, just that it seems to get the job done with few complaints from the devs who commit my patches. It’s also a good method to use on Windows. (Sorry, someone else can document command-line Subversion use - not that I don’t know it, I’m just lazy.) Here we go…