Home/ Questions/Q 186599
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T15:40:31+00:00

This may be impossible, but I’m going to ask anyway. Without going into the

  • 0

This may be impossible, but I’m going to ask anyway.

Without going into the details of why it’s like this, I have two primary checkouts that I work in, one for the production release branch, and one for trunk. Each of them is a small collection of svn:externals references to sub-projects, with no direct content under the checked-out svn directory.

That is, the four svn:externals directives add all of the content in each of the checkout directories.

When I do a commit via Eclipse(/Subclipse) I can commit changes across all of the external projects in one go, which is good because they’re just separate sub-projects in the same repository and this allows me to avoid doing 4 separate commits in a row to the same repo.

Is it not possible to do the same thing from the command line? Commits for each of the externals could certainly be scripted and aliased to one command, but I’d rather avoid cluttering the commit log with separate commits for related changes if possible.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Unfortunately, your assumption was correct. The current subversion command line tool will not recurse into disjointed externals working copies during a commit. Eclipse probably figures out that it’s all rooted the same and adjusts everything so that it’s only doing a single commit transaction.

    This drawback of the client is actually listed as one of the issues to watch out for when defining externals in your project. As of the 1.6.1 client, this limitation still exists.

    • 0