This documentation was written to describe the 1. You can get new files into your Subversion repository in two ways: svn import and svn add. We'll discuss svn import now and will discuss svn add later in this chapter when we review a typical day with Subversion.
The svn import command is a quick way to copy an unversioned tree of files into a repository, creating intermediate directories as necessary. You typically use this when you have an existing tree of files that you want to begin tracking in your Subversion repository. For example:. Note that you didn't have to create that new directory first— svn import does that for you. Immediately after the commit, you can see your data in the repository:. Note that after the import is finished, the original local directory is not converted into a working copy.
To begin working on that data in a versioned fashion, you still need to create a fresh working copy of that tree. Subversion provides the ultimate flexibility in terms of how you arrange your data. Because it simply versions directories and files, and because it ascribes no particular meaning to any of those objects, you may arrange the data in your repository in any way that you choose.
Use the repository browser to create a new project folder directly in the repository. If you are using one of the standard layouts you will probably want to create this as a sub-folder of trunk rather than in the repository root. The repository browser shows the repository structure just like Windows explorer, so you can see how things are organised. Checkout the new folder over the top of the folder you want to import. You will get a warning that the local folder is not empty. Ignore the warning.
Now you have a versioned top level folder with unversioned content. You can add and remove files, set svn:ignore properties on folders and make any other changes you need to. Commit the top level folder, and you have a new versioned tree, and a local working copy, created from your existing folder.
Sometimes you need to have a file under version control which contains user specific data. In such cases we suggest to use template files. You create a file which contains all the data your developers will need, add that file to version control and let the developers check this file out.
Then, each developer has to make a copy of that file and rename that copy. After that, modifying the copy is not a problem anymore. As an example, you can have a look at TortoiseSVN's build script. It calls a file named default. The working copy will be populated with your files. If everything looks right you can continue working from there. Same as you would do with any SVN system. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Collectives on Stack Overflow. Learn more. Ask Question. Asked 11 years, 10 months ago. Active 8 years, 7 months ago. Viewed 42k times. I don't find any option for that in my dashboard. I am using tortoiseSvn on my computer , so how to upload files and configure tortoiseSvn? Radi Radi 6, 16 16 gold badges 58 58 silver badges 89 89 bronze badges.
Add a comment. Active Oldest Votes. Now for importing the files proper I see at least two methods. Method 1 - Selectively commit the files Right-click in the folder of your choice and select Checkout
0コメント