Add new comment

Posted on by Brad Czerniak (not verified).

Is version tracking Drupal core or things in contrib that you tend not to hack really a best practice?

In <a href="http:// hawidu.com/2011/12/09/drupal-and-git/">a presentation to DrupalCamp Michigan about git</a>, I tried to make the case that your version control environment should be reusable units; a custom module for one site might be appropriate for a later site, for instance. Things like core and contrib, unless they're necessary to edit, can best be controlled, deployed, and upgraded when left to their own devices.

There's an appeal to organizing site files as a cohesive whole. I just wonder whether this strategy is more manageable than a drush-and-other-stuff technique.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.