[support] Planning upgrade

William Smith william.darren at gmail.com
Sat Aug 25 15:45:35 UTC 2007


I always find it a good idea that if I absolutely must patch or manually
modify a contrib module, to first copy the original to something like
modulename.module.orig so that I can easily find which module(s) have been
modified, and can do a diff to see exactly what those changes were at a
later date (such as upgrading the module, etc..).  Just a little tip,
hopefully it helps you out in the future.

William


On 8/25/07, A-NO-NE Music <madflute at anonemusic.com> wrote:
>
> Cog Rusty / 2007/08/25 / 09:29 AM wrote:
> >Perhaps if you remember why you modified it, it would help finding
> >which one you modified (or whether it matters now).
>
> It was a patch required by a module, which I don't remember what module
> that was.  The patch didn't run so I had to hack manually.  Anyway,
> lesson learned.
>
> I need to go over Earnie's response to think hard for re-planning.
>
>
> --
>
> - Hiro
>
> Hiroaki Honshuku, A-NO-NE Music, Boston, MA
> <http://a-no-ne.com> <http://anonemusic.com>
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20070825/d9ec7ffa/attachment-0001.htm 


More information about the support mailing list