On Wed, Aug 26, 2015 at 9:36 AM, Julian Foad <julianf...@btopenworld.com> wrote:
> Jörg Rebenstorf wrote: > > I have a suggestion for a solution of issue 2516 [...] > > First, let me quote the summary line and URL of issue 2516, for easier > reference: > > http://subversion.tigris.org/issues/show_bug.cgi?id=2516 > > "--revision option is not forwarded to svn:externals references" > > [...] > > The new access option should update the working copy of the primary > > target "PATH..." and its externals to a certain inter-repository > > consistent state, that is, to update the primary target and all of its > > externals content to their appropriate version at a certain point in > > time. > > The new access method shall be an additional command-line option, for > > example "--sync-externals", for the svn client tool's update command > > like: > > Why do we even need to introduce a new option here? What would be controversial about just doing this automatically (for externals from the same repository that do not specify a revision in the external)? Isn't this just the expected and desired behavior? -- Thanks Mark Phippard http://markphip.blogspot.com/
