Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3969336
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T03:57:06+00:00 2026-05-20T03:57:06+00:00

Our Subversion repository has several subdirectories containing shared files as well as subdirectories for

  • 0

Our Subversion repository has several subdirectories containing shared files as well as subdirectories for each project. Projects are set up with relative svn:externals properties to pull in shared directories out of the repository and set them up as subdirectories.

So, for example, our repostory looks something like this:

client
shared
portable
app1
app2

and app1 has as its svn:externals

../shared shared
../portable portable

so that on checkout, portable and shared are usable as subdirectories of app1.

TortoiseSVN has the nifty feature that doing a commit on app1 will automatically detect the externals subdirectories, realize that they’re all part of the same repository, and
commit all their changes as part of the same commit. However, I can’t figure out how to get the same behavior out of the command-line client. Any suggestions?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T03:57:06+00:00Added an answer on May 20, 2026 at 3:57 am

    It turns out that this has a very simple solution, at least with Subversion 1.6.12: explicitly specify paths on the command line.

    For example, if I run

    cd app1
    svn ci file_in_repository.cpp shared portable
    

    then Subversion will commit app1, shared, and portable all within one revision, as I want it to. Apparently the command-line client won’t process externals by default but has no difficulty handling a single commit with them if they’re explicitly given.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We use Subversion as our source control system and store the VisualStudio project files
Presently, we've got several main projects each in their own repository. We will have
I recently began importing a number of our projects into a Subversion repository at
We've got VisualSVN Server set up as our Subversion server on Windows, and we
Our team (5-10 developers) plans to adopt Subversion for our .NET (Visual Studio) projects/solutions
We have moved our subversion repository to a different server. I have run svn
We are looking at writing a site using Lucene.Net to search our Subversion repository
I've got a Subversion repository that our Atlassian Fisheye instances nearly chokes on because
We moved our projects (SQL Server and .Net) from Visual-Source-Safe to SubVersion. We have
CentOS 5.3 subversion 1.4.2 Our company would like to know who has checked out

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.