You could use &#39;diff&#39; or something similar to find out what&#39;s changed and put just those lines of CSS in a file in your theme folder.  Generally, I find the best way to avoid this problem is not to get into it in the first place by keeping the custom CSS in the theme folder to begin with.  :)<div>
<br></div><div>Brian<br><br><div class="gmail_quote">On Wed, Dec 22, 2010 at 5:52 PM, Marty Landman <span dir="ltr">&lt;<a href="mailto:mlandman@face2interface.com">mlandman@face2interface.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I&#39;ve upgraded a D5 website for a client and the CSS files for<br>
nice_menus had been customized within the nice_menus module&#39;s<br>
directory, which obviously got overwritten by my upgrade.<br>
<br>
Which I understand is why this wasn&#39;t the right way to do things. I&#39;m<br>
sure that copying the old css files fixes the problems, because I<br>
did. Want to do things according to best practice. I could just take<br>
those entire css file contents and append them to the style.css file<br>
for the theme. That&#39;d work I think, but is there a better way, w/o<br>
actually picking all the lines apart to see what&#39;s needed?<br>
<br>
Marty<br>
<font color="#888888"><br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</font></blockquote></div><br><br clear="all"><br>
</div>