On 04/17/2013 11:32 AM, Philip Martin wrote: > "C. Michael Pilato" <cmpil...@collab.net> writes: > >> On 04/17/2013 09:43 AM, Philip Martin wrote: >>> The behaviour looks simple to define for 'patch' and 'merge', I was >>> thinking about 'svn add --force' which marks all the unversioned files >>> for addition. >> >> You mean, perhaps, 'svn add --force -R' (or some other non-empty depth). > > Add is recursive by default.
Doh. You're right, of course. >> But that marks files *and* directories for addition. >> directories to changelists today. :-( > > I imagine a new add-to-changelist option for commands would skip > directories much like 'svn changelist'. But even if we do that it's not > clear (to me anyway) which files should be added by 'svn add --force'. Let's examine the feasible options: 1. Mark all files under the explicit 'svn add' target with changelist. Meh... 'svn changelist -R' would do the same. 2. Mark only files added to version control by this command. To do this with a subsequent 'svn changelist' command would require a bit of scripting magic, so this seems like an interpretation that actually provides benefit. -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Enterprise Cloud Development
signature.asc
Description: OpenPGP digital signature
