If you're importing a new resource directly to the repository, then they have to be serial, but when staging changes in a local working copy, adding a resource tells SVN that it should be added when that particular resource path is committed, but I find it most useful to add multiple items and make any modifications to use them before committing, as Gabe alluded to.
You could potentially write a script to do what you're asking from Terminal, but since Versions links directly against the SVN libraries, this feature (which is of dubious value, I would suggest) would have to be added at the application level. To my knowledge, nearly all version control systems work this way, so I expect SVN to do the same. If I may humbly suggest, it's nearly always preferable that Subversion work this way. I can think of a handful of times I've committed changes without adding a file, but they're few and far between. - Quinn On Mar 29, 2010, at 9:51 PM, Alex Zavatone wrote: > One after the other. It's a client to server, then client to server set of > commands. Wait for one to finish. > > Cheers, > - Alex > > On Mar 29, 2010, at 10:43 AM, daberhasher wrote: > >> Hi, >> >> I'm a new Versions user and I'm trying to figure out a way to add new >> files automatically by committing any changes (in this case the >> addition of extra files to the folder). Can it be done? I've noticed >> that I have to first add the new files to the repository and then >> commit. If there is any way around this, any help would be >> appreciated. >> >> Thank you.
smime.p7s
Description: S/MIME cryptographic signature
