Ignore branches in working copy of SVN

Question

Recently, we made the first branch of our project. The string is quite large (several GB), which does not matter for the server, because the branch is created through efficient communication. However, in client working copies, the project does take up twice as much space (our entire WC is from the root of the repository).

Since only a few people really need a branch, how can others ignore (i.e. not download) all branches using TortoiseSVN?

Users checking the trunk, as suggested below, are not a solution here. Our structure is as follows:

/
 projects
  project-x
   assets
    blabla.psd
   code
    trunk
    branches
     branch1
     branch2
  project-y
   ...

Answer 1

- /trunk. , , , /root/trunk /root. , , .

- , , . , , , :

• checkout from root " "
• checkout from root/trunk "full recursive"

- , - , :

• checkout from root/branches " "
• " "

SVN, " .

. TortoiseProc.

EDIT: , - , " " , , checkout dept "". " ". , .

. .

UPDATE: TortoiseSVN 1.7 "Checkout" " ", . " ".

Answer 2

( )

find . -name branches -exec svn update --set-depth empty {} \;

, . , , :

svn update --set-depth infinity branches\my-feature-branch

Answer 3

, , :

repo root
  |
  +-- trunk
  |
  +-- branches
         |
         +-- branch1
         +-- branch2
         +-- ...

, http://server/repo/trunk http://server/repo, , http://server/repo/branches/branch1.

Answer 4

, , " ...". " " "". (, .) , . , .

, ( ..) "Repo Browser". , " ". ; , , " "

TortoiseSVN

Answer 5

If people need to load assets along with code, it's more natural to fork at project-x level. In this case, you will not have the problems that you describe. Do you have any reason to branch only parts of your material?