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 298195
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T06:42:33+00:00 2026-05-12T06:42:33+00:00

I have a subversion repo with directories that contain the usual source-controlled files, but

  • 0

I have a subversion repo with directories that contain the usual source-controlled files, but in addition to that contain files that are a dependency for execution, but not checked into source control and instead added as svn:ignore (since they would be kept in duplicates all around the repo if they were checked in into all folders). (believe me or not but there is a reason that is at least half good for having this duplication of the ignored files 😉 )

Sometimes I want to branch out and make a local copy of the directory to do a certain defined development task, and then merge back into the trunk after a couple of checkins. When I take such a copy/branch of the folder, is there a way to make it copy all the files, including the svn:ignored ones as well into the newly created branch folder working copy (what I currently do is copying them over by hand after having used tortoise to create the branch)
(but of course also still keep the :ignored files off the repo)

Many thanks in advance for help!

  • 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-12T06:42:34+00:00Added an answer on May 12, 2026 at 6:42 am

    I believe that the answer is no, because Subversion doesn’t know anything about those files, it thinks that you really want them to always be ignored. In fact, one of the methods of branching involves copying from one point in the repository to another (URL -> URL, whereas you are presumably talking about copying from the working copy to a branch) in which case there are no “ignored” files since it is copying directly between bits of the repository.

    Though I don’t see why the Subversion developers couldn’t add a new feature to allow automatic copies of svn:ignore‘d files when copying from a working copy (WC -> URL or WC -> WC).

    It might not be difficult to write a script that checked the svn:ignore properties, and matched (just like svn does) those files, then copied them across too.

    The command

    svn status --no-ignore | grep '^I'
    

    should give you a list of all ignored files. Pipe through sed to clean up the line, then xargs and you can quickly copy the files across. Albeit not automatically, which is what you are looking for.

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

Sidebar

Related Questions

From what I understand of subversion if you have a repo that contains multiple
I have a repository that is currently using Subversion, but I'd like to use
I have a Subversion repository called 'repo'. Inside of repo are trunk/ and branches/
We have a non-standard subversion respository that we would like to convert to Git.
On my server I have subversion installed, but I accidently removed the .svn folder
I recently converted a subversion repo, which had been converted from cvs before that
I have a subversion repo with the following layout: svnrepo/projectA/trunk svnrepo/projectA/tags svnrepo/projectA/branches svnrepo/projectB/trunk svnrepo/projectB/tags
I have problem with my own Subversion repository. It worked yesterday. But I received
We have the following structure in our Subversion repo: Here is a quick summary:
I'd like to have git automatically push local changes to the upstream subversion repo

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.