Thanks again to Larry and Andrew for their responses: really helpful!<br><br>Just thought I'd let folks know that I've updated/upgraded the list of commands on the <a href="http://drupal.org/node/477684">Drush handbook page</a>. I've also created a printer friendly pdf of that list since since it's nice to have printed cheat sheets for command-line stuff.<br>
<br>The pdf is at: <a href="http://drupal.org/files/drush-cheat-sheet.pdf">http://drupal.org/files/drush-cheat-sheet.pdf</a><br><br>The handbook page is at: <a href="http://drupal.org/node/477684">http://drupal.org/node/477684</a><br>
<br>Best,<br><br>Shai<br><br><div class="gmail_quote">On Wed, Nov 25, 2009 at 12:56 AM, Larry Garfield <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;">
Possibly. Or svn ignore. Unfortunately as far as I know you can't set a<br>
server-wide ignore list, so I've never bothered to set it up for all of our<br>
developers. (Some may have done it themselves. I'm not sure.) For my part I<br>
do nearly everything from the Linux command line ssh'ed into the dev server,<br>
so it's rarely an issue for me. :-)<br>
<div><div></div><div class="h5"><br>
On Tuesday 24 November 2009 8:07:56 pm Shai Gluskin wrote:<br>
> Thanks Larry and Andrew!<br>
><br>
> Larry, can you use --exclude to deal with the OS X crap?<br>
><br>
> Shai<br>
><br>
> On Tue, Nov 24, 2009 at 8:38 PM, <a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a> <<br>
><br>
> <a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a>> wrote:<br>
> > SVN isn't quite as bad for this as you make it out to be. :-) You can<br>
> > do:<br>
> ><br>
> > svn add --force sites/all/modules<br>
> ><br>
> > and it will recursively add any files under that directory that it<br>
> > doesn't already know about. Be careful of ._ files and similar crap that<br>
> > OS X may create. :-)<br>
> ><br>
> > That's actually my usual workflow at this point. Drush dl to grab new<br>
> > modules, drush update to update a module, followed by the svn command<br>
> > above and then commit. It doesn't handle file deletes or major file<br>
> > reorganization, but those are quite rare.<br>
> ><br>
> > And I almost never check out a module straight from CVS. If I want a dev<br>
> > version, you can tell Drush to get that for you.<br>
> ><br>
> > --Larry Garfield<br>
> ><br>
> > Shai Gluskin wrote:<br>
> >> I get modules from d.o. from CVS, then I commit them to my own<br>
> >> repository with SVN.<br>
> >><br>
> >> When updating modules I've doing SVN del, CVS co, SVN add instead of<br>
> >> simply CVS up because of orphaned and new files. SVN freaks out over<br>
> >> orphans and the new files are just a pain since you need to SVN add for<br>
> >> each one.<br>
> >><br>
> >> But I just installed Drush and I'm so excited about making all this<br>
> >> 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<br>
> >> dealing with orphans and new files?<br>
> >><br>
> >> Thanks,<br>
> >><br>
> >> Shai<br>
<br>
</div></div><div><div></div><div class="h5">--<br>
Larry Garfield<br>
<a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a><br>
</div></div></blockquote></div><br>