You are here

Home » API reference » Patch manager 6

README.txt in Patch manager 6

Same filename and directory in other branches
  1. 7 README.txt
<?php

Patch manager provides a developer tool for managing patches
to core and contributed modules.


CONTENTS OF THIS FILE
---------------------

 * Requirements
 * Patch naming
 * Configuration
 * More Information

REQUIREMENTS
------------

The patch_manager module requires the following modules:
  cck (content submodule)
  cck (text submodule)
  filefield
  views
  filefield_paths (optional)
  views_bulk_operations (optional)

It helps to have a working patch binary on your system that
is executable by the webserver user.

Please note!: You have to download CCK project manually, because we can't put
  a dependency as there is no cck module inside cck project.

PATCH NAMING
------------

If you have filefield_paths installed (with token, and pathauto),
this will allow you to automatically rename patch files. The
Drupal suggested naming scheme is:
  module-description-issue-comment.patch

With tokens, this would be:
  [field_module-raw]-[title]-[field_drupal_issue-raw].patch
  
You can set this up here:
  /admin/content/node-type/patch/fields/field_patch


CONFIGURATION
-------------

Access the configuration page to set the path to your patch
binary. This will allow you to patch and reverse patches through
the administration interface.
  /admin/build/patch

You can start adding patches immediately, as you would a normal node:
  /node/add/patch

You can modify the default fields to store extra information via
the content module:
  /admin/content/node-type/patch/fields
  
Everything is powered by Views, so you can modify or create new views:
  /admin/build/views/edit/patches


MORE INFORMATION
----------------

See the project page at:
  http://drupal.org/project/patch_manager

File

README.txt
View source 
  2. 

  3. Patch manager provides a developer tool for managing patches

  4. to core and contributed modules.

  5. 

  6. 

  7. CONTENTS OF THIS FILE

  8. ---------------------

  9. 

  10.  * Requirements

  11.  * Patch naming

  12.  * Configuration

  13.  * More Information

  14. 

  15. REQUIREMENTS

  16. ------------

  17. 

  18. The patch_manager module requires the following modules:

  19.   cck (content submodule)

  20.   cck (text submodule)

  21.   filefield

  22.   views

  23.   filefield_paths (optional)

  24.   views_bulk_operations (optional)

  25. 

  26. It helps to have a working patch binary on your system that

  27. is executable by the webserver user.

  28. 

  29. Please note!: You have to download CCK project manually, because we can't put

  30.   a dependency as there is no cck module inside cck project.

  31. 

  32. PATCH NAMING

  33. ------------

  34. 

  35. If you have filefield_paths installed (with token, and pathauto),

  36. this will allow you to automatically rename patch files. The

  37. Drupal suggested naming scheme is:

  38.   module-description-issue-comment.patch

  39. 

  40. With tokens, this would be:

  41.   [field_module-raw]-[title]-[field_drupal_issue-raw].patch

  42.   

  43. You can set this up here:

  44.   /admin/content/node-type/patch/fields/field_patch

  45. 

  46. 

  47. CONFIGURATION

  48. -------------

  49. 

  50. Access the configuration page to set the path to your patch

  51. binary. This will allow you to patch and reverse patches through

  52. the administration interface.

  53.   /admin/build/patch

  54. 

  55. You can start adding patches immediately, as you would a normal node:

  56.   /node/add/patch

  57. 

  58. You can modify the default fields to store extra information via

  59. the content module:

  60.   /admin/content/node-type/patch/fields

  61.   

  62. Everything is powered by Views, so you can modify or create new views:

  63.   /admin/build/views/edit/patches

  64. 

  65. 

  66. MORE INFORMATION

  67. ----------------

  68. 

  69. See the project page at:

  70.   http://drupal.org/project/patch_manager

  71.