Svn In-Place Import and Checkout

SVN in-place import and checkout

Let's say you've used svnadmin to create a repository at /svn/foo/mydirname, and you want to version control /home/user/mydirname (is that what you mean?).

Then do the following:

cd /home/user/mydirname
svn co file:///svn/foo/mydirname . #This only creates the ".svn" folder for version control
svn add ./*                        #Tell svn you want to version control all files in this dir
svn ci                             #Check the files in

Your directory is now version controlled!

What is the difference between svn import and checkout?

"import" and "checkout" are polar opposites.

"Import" is to bring something completely outside of version control into SVN.

Once something is under SVN control, you can "commit" (new modifications), or "checkout" (stuff you've already committed).

At any time, you can "export" some or all of your project into a "clean directory". The source you've exported is not under version control.

You "import into" and "export out of" SVN.

You "commit" and "checkout" stuff that's already under SVN control.

How to checkout an svn repository to your local machine

1. "putty with my university Id" means (at least) SSH-access to remote host and nohow define existence and accessibility of http-based SVN-server. You may have svn+ssh:// access, if it's configured at server side (ask admin for possibility and credentials)
2. You must to read description of svn import command at least and get all needed parameters in order to use command properly in remote shell. For svn import [PATH] URL you miss URL (of real repository) definition. Ask admin about it

SVN at command line - how to import, then commit

The SVN import command is a quick way to copy an unversioned tree of files into a repository, creating intermediate directories as necessary. SVN import doesn't require a working copy, and your files are immediately committed to the repository.

But in order to do svn add or svn commit, you should be inside the working directory. First you have to check out the files from SVN, then modify it as per the requirement, then svn add and svn commit from the working directory should work.

How to import an already checked out svn repository into Eclipse?

"Import..." the existing project then "Share..." the project. The Subversive (or SubClipse) client will realize that the project has a .svn folder and reattach to the repository.

Correct way of importing a project in SVN?

You could create the layout in SVN directly if you wanted; using step 3) in your question makes it easier as it allows all in one go. If you follow it, you do not need that initial folder after the import. In fact, the folder you do the import from is not placed under version control, so changes made there will not make it back to the repository

As for the layout: it is customary to do so, but SVN does not impose a restriction: you could organize your project the way you want. The traditional logic is:

• trunk denotes the latest known working copy
• branches have sub folders that denote various development efforts (possibly by separate people) -- e.g. for a particular bug fix. You work on it not afected by changes to the trunk or other branches, then merge your changes to the trunk when you are ready.
• tags are marked versions of the trunk to denote the state of the trunk at a particular time/stage -- this is to allow easy location of what belongs to the same release, for example, instead of having to remember several version numbers

---

Related Topics