<html><body bgcolor="#FFFFFF"><div>Use git-svn and then you have got branches (which areuch easier to merge than svn branches) and you also get git add interactive and hit stash as well.<br><br>Sent from my iPhone.<div><br></div></div><div><br>On Apr 28, 2010, at 7:42 AM, nan wich <<a href="mailto:nan_wich@bellsouth.net">nan_wich@bellsouth.net</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div style="font-family:arial, helvetica, sans-serif;font-size:14pt;color:#7f003f;"><div></div>
<div>At my current location, I have developed a major site-specific module (well over 100K). I have already split the admin, pages, and blocks out into separate files. I have largely done this on the same model as I use for my DO contribs.</div>
<div> </div>
<div>At any given time I may have four or five changes in place at various stages of testing, and working on the next change. The problem is that the powers-that-be occasionally want one change moved to production quickly. I can't do that without potentially moving untested changes too.</div>
<div> </div>
<div>So I'm looking for ways that others get around this situation. Certainly I can move various smaller pieces into include files; this is not a major problem as we use eAccelerator to cache all the modules any way. Is that the best way or only way? We do have SVN available.<br> </div>
<p><font face="bookman old style, new york, times, serif" color="#ff007f" size="4"><em><strong>Nancy E. Wichmann, PMP</strong></em></font></p>
<p><font face="arial, helvetica, sans-serif">Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.</font></p>
<div></div></div></div></blockquote></body></html>