On Mon, Jun 17, 2013 at 2:28 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> The 1.8 release notes read as follows:
> The svn commit command supports a new --include-externals option, which
> causes it to commit changes within externals in the current working
> copy, in addition to the changes in the current working copy. This works
> by implicitly adding all externals within the commit target to the list
> of commit targets.
> My testing seems to show that we do not appear to commit externals pulled
> from a different repository than the primary working copy. Can someone
> confirm this? Is there a technical reason not to do this? Obviously we
> can't do a multi-repository atomic commit, but I could have sworn that at
> one time this feature would sort the committables by repository, then issue
> one commit per repository (with the opportunity to compose a log message for
> each commit grouping). Maybe I'm just delusional?
We use the feature you describe in Subclipse via JavaHL (talking about
SVN 1.7.x). It works provided that you name all the targets on the
commit API call, which we do from Subclipse.
We are not planning to use this new --include-external feature since
it mainly seems to imply to the implicit traversal done when only a
top-level target(s) is named.
Hopefully explicitly naming targets still works, but yes it sounds
like this feature ought to support it too.
Received on 2013-06-17 20:36:27 CEST