patch
Testing patches for Drupal from a Windows machine
There are various approaches to getting a usable development environment working on a Microsoft Windows machine. Here are some:
VirtualBox
Best bet, virtualbox? Let's you make believe you're actually on, say Debian Linux.
Reset your Drupal checkout so that it is clean and ready to try more patches
$ cvs update -C
(Locally modified node.admin.inc moved to .#node.admin.inc.1.24)
(Locally modified node.module moved to .#node.module.1.974)
(Locally modified taxonomy.admin.inc moved to .#taxonomy.admin.inc.1.27)
(Locally modified taxonomy.module moved to .#taxonomy.module.1.425)
(Locally modified taxonomy.test moved to .#taxonomy.test.1.3)
Patch naming conventions for Drupal core and contrib
webchick talking to Michelle in IRC #drupal:
I name all my patches as {module_name}-{description-of-changes}-{issue_node_id}-{issue_comment_id}.patch
How to make patch files to contribute to contributed modules
These instructions assume a GNU-Linux, Mac OS X, or other UNIX-y computing environment.
Follow these instructions for using CVS:
http://drupal.org/patch/create
However, if you are making a patch for a contributed module rather than Drupal core, going to the Drupal root directory doesn't make sense.
How to apply a patch to a Drupal module
Following the Drupal documentation on applying patches.
The module localization client, originally developed for Drupal 6, needs a patch to the Drupal core module, locale (note that while locale is core it is also optional and disabled by default).
