On 08/29/2011 05:48 PM, C. Michael Pilato wrote: > No sweat. 'svn commit --include-externals' sounds like a fine plan.
+1 and volunteering. So by default, *all* externals shall be skipped from commit (dir and file externals alike). When --include-externals is passed to 'svn commit', *all* externals are recursed into (dir and file externals alike). However, an external that has a specific peg revision (file and dir externals alike) is never recursively included in commit. Questions remain about passing externals explicitly: - when an external is passed as explicit target, still require --include-externals? - when a *pegged* external is passed as explicit target (and say even if --include-externals is passed), should we *still* refuse to commit it? I'd say yes (thinking of 'svn commit *') and yes (thinking of avoiding inconsistent external state as seen with file externals, and of changes snapping back to peg as seen with dir externals). If user wants to commit to a *pegged* external, user should just use a different, non-externals-ized checkout. ~Neels
signature.asc
Description: OpenPGP digital signature
