Possibly. Or svn ignore. Unfortunately as far as I know you can't set a server-wide ignore list, so I've never bothered to set it up for all of our developers. (Some may have done it themselves. I'm not sure.) For my part I do nearly everything from the Linux command line ssh'ed into the dev server, so it's rarely an issue for me. :-)
On Tuesday 24 November 2009 8:07:56 pm Shai Gluskin wrote: > Thanks Larry and Andrew! > > Larry, can you use --exclude to deal with the OS X crap? > > Shai > > On Tue, Nov 24, 2009 at 8:38 PM, [email protected] < > > [email protected]> wrote: > > SVN isn't quite as bad for this as you make it out to be. :-) You can > > do: > > > > svn add --force sites/all/modules > > > > 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. :-) > > > > 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. > > > > 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. > > > > --Larry Garfield > > > > Shai Gluskin wrote: > >> I get modules from d.o. from CVS, then I commit them to my own > >> repository with SVN. > >> > >> 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. > >> > >> 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. > >> > >> So if you commit CVS versions of contrib to SVN, what is your method for > >> dealing with orphans and new files? > >> > >> Thanks, > >> > >> Shai -- Larry Garfield [email protected]
