Home ›
Patch naming conventions for Drupal core and contribPatch naming conventions for Drupal core and contrib
Submitted by Benjamin Melançon on September 13, 2008 - 1:59pm
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
Personally, I think issue_comment_id might be hard to do (even interpreted as the big #5 etc project module places in the comment title, rather than the internal Drupal ID!) since people can add comments while you are making the patch, but I'm on board with the ideal.
Getting into that habit also really forces you to keep to a one-issue-one-change thing.
It's like she knows I'm listening!
Resolution
Searched words:
Naming standards for Drupal code patches
Comments
Drupal handbook page
There is a drupal.org handbook page that has this information too.
It's at http://drupal.org/patch/submit
In regards to the comment ID part, if you are in the habit of previewing your comments before posting you will avoid this most of the time as the preview will have your comment number and you can quickly rename if necessary. So it would then only be an issue very rarely when a person posts only between the time you preview and submit.
Post new comment