Thanks Larry and Andrew!<br><br>Larry, can you use --exclude to deal with the OS X crap?<br><br>Shai<br><br><div class="gmail_quote">On Tue, Nov 24, 2009 at 8:38 PM, <a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a> <span dir="ltr"><<a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">SVN isn't quite as bad for this as you make it out to be. :-) You can do:<br>
<br>
svn add --force sites/all/modules<br>
<br>
and it will recursively add any files under that directory that it doesn't already know about. Be careful of ._ files and similar crap that OS X may create. :-)<br>
<br>
That's actually my usual workflow at this point. Drush dl to grab new modules, drush update to update a module, followed by the svn command above and then commit. It doesn't handle file deletes or major file reorganization, but those are quite rare.<br>
<br>
And I almost never check out a module straight from CVS. If I want a dev version, you can tell Drush to get that for you.<br>
<br>
--Larry Garfield<div><div></div><div class="h5"><br>
<br>
Shai Gluskin wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I get modules from d.o. from CVS, then I commit them to my own repository with SVN.<br>
<br>
When updating modules I've doing SVN del, CVS co, SVN add instead of simply CVS up because of orphaned and new files. SVN freaks out over orphans and the new files are just a pain since you need to SVN add for each one.<br>
<br>
But I just installed Drush and I'm so excited about making all this easy. So I'm motivated to finally ask for help around this.<br>
<br>
So if you commit CVS versions of contrib to SVN, what is your method for dealing with orphans and new files?<br>
<br>
Thanks,<br>
<br>
Shai<br>
</blockquote>
</div></div></blockquote></div><br>