SVN West Tutorial: Introduction for New Users

By /

Okay, here’s a lengthy article (approximately 5000 words) providing a detailed SVN West tutorial and introduction for new users. This will cover a wide range of topics, from basic concepts to practical usage, and include explanations, examples, and best practices.

SVN West Tutorial: Introduction for New Users

Table of Contents

  1. Introduction: What is SVN and Why Use SVN West?

    • 1.1 What is Version Control?
    • 1.2 What is Subversion (SVN)?
    • 1.3 What is SVN West?
    • 1.4 Why Choose SVN West?
    • 1.5 Alternatives to SVN West

  2. Getting Started: Setting Up Your Environment

    • 2.1 Creating an SVN West Account
    • 2.2 Installing a Subversion Client
      • 2.2.1 TortoiseSVN (Windows)
      • 2.2.2 SmartSVN (Cross-Platform)
      • 2.2.3 Command-Line Client (Linux/macOS/Windows)
      • 2.2.4 Choosing the Right Client
    • 2.3 Connecting to Your SVN West Repository

  3. Core Concepts: Understanding the SVN Workflow

    • 3.1 Repository
    • 3.2 Working Copy
    • 3.3 Trunk, Branches, and Tags
      • 3.3.1 Trunk (Mainline Development)
      • 3.3.2 Branches (Feature Development, Bug Fixes)
      • 3.3.3 Tags (Release Snapshots)
    • 3.4 Revisions
    • 3.5 Commits
    • 3.6 Updates
    • 3.7 Conflicts
    • 3.8 The SVN Workflow Diagram

  4. Basic Operations: Working with Your Repository

    • 4.1 Checkout: Getting a Working Copy
    • 4.2 Update: Synchronizing Your Working Copy
    • 4.3 Add: Adding New Files and Directories
    • 4.4 Commit: Saving Changes to the Repository
      • 4.4.1 Writing Good Commit Messages
    • 4.5 Delete: Removing Files and Directories
    • 4.6 Move/Rename: Restructuring Your Project
    • 4.7 Revert: Undoing Local Changes
    • 4.8 Status: Checking the Status of Your Working Copy
    • 4.9 Ignoring Files and Directories (svn:ignore)

  5. Branching and Merging: Managing Parallel Development

    • 5.1 Creating a Branch
    • 5.2 Switching Between Branches
    • 5.3 Merging Changes from a Branch to Trunk
    • 5.4 Merging Changes from Trunk to a Branch
    • 5.5 Handling Merge Conflicts
      • 5.5.1 Identifying Conflicts
      • 5.5.2 Resolving Conflicts Manually
      • 5.5.3 Using Merge Tools
    • 5.6 Best Practices for Branching and Merging

  6. Tagging: Creating Release Snapshots

    • 6.1 Creating a Tag
    • 6.2 Checking Out a Specific Tag

  7. Inspecting History: Exploring the Repository’s Past

    • 7.1 Log: Viewing Commit History
    • 7.2 Diff: Comparing Revisions
    • 7.3 Blame/Annotate: Identifying Who Changed What and When
    • 7.4 Revision Graph (Visualizing History)

  8. Advanced Topics

    • 8.1 SVN Properties
      • 8.1.1 svn:eol-style
      • 8.1.2 svn:keywords
      • 8.1.3 svn:mime-type
      • 8.1.4 svn:externals
    • 8.2 Locking
      • 8.2.1 When to Use Locking
      • 8.2.2 How to Lock and Unlock Files
    • 8.3 Hooks
    • 8.4 Using svnadmin (for Repository Administrators)

  9. SVN West Specific Features (if any)

  10. Best Practices and Tips

    • 10.1 Commit Frequently
    • 10.2 Update Regularly
    • 10.3 Write Clear Commit Messages
    • 10.4 Use Branches Effectively
    • 10.5 Plan Your Repository Structure
    • 10.6 Back Up Your Repository
    • 10.7 Communicate with Your Team

  11. Troubleshooting Common Issues

    • 11.1 “Out of Date” Errors
    • 11.2 “Tree Conflict” Errors
    • 11.3 “Needs Lock” Errors
    • 11.4 Connection Problems
    • 11.5 Corrupted Working Copy

  12. Conclusion

1. Introduction: What is SVN and Why Use SVN West?

1.1 What is Version Control?

Version control, also known as source control or revision control, is a system that records changes to a file or set of files over time so that you can recall specific versions later. This is crucial for software development, but it’s also useful for any project involving collaborative work on documents, configurations, or any other type of file.

Imagine working on a document with multiple people without version control. You might end up with numerous copies of the file (e.g., document_v1.docx, document_v2_john.docx, document_v3_final_really.docx), making it difficult to track changes, merge contributions, and revert to earlier versions. Version control solves this problem by providing a centralized system for managing changes.

1.2 What is Subversion (SVN)?

Subversion (SVN) is a centralized version control system (CVCS). This means there’s a single, central repository that stores all the versions of the project’s files. Users “check out” a working copy of the project from this central repository, make changes locally, and then “commit” those changes back to the repository.

Key features of SVN include:

  • Atomic Commits: Changes are committed as a single, indivisible unit. Either all changes are saved, or none are. This prevents partial commits that could leave the repository in an inconsistent state.
  • Revision History: SVN maintains a complete history of every change made to the repository, allowing you to easily revert to any previous version.
  • Branching and Merging: SVN supports creating branches, which are separate lines of development, and merging changes between branches. This enables parallel development and feature isolation.
  • Tagging: SVN allows you to create tags, which are snapshots of the repository at a specific point in time, typically used for releases.
  • Access Control: SVN provides mechanisms for controlling user access and permissions to the repository.

1.3 What is SVN West?

SVN West is a hosting provider that offers Subversion repository hosting services. Think of it like a web hosting company, but instead of hosting websites, they host SVN repositories. They provide the server infrastructure, manage the Subversion server software, and handle backups and security. You, as the user, interact with your repository through an SVN client.

1.4 Why Choose SVN West?

SVN West offers several advantages:

  • Ease of Use: They handle the complexities of setting up and maintaining an SVN server, allowing you to focus on your project.
  • Reliability: They provide reliable infrastructure and backups to ensure your data is safe.
  • Scalability: They can accommodate projects of various sizes.
  • Support: They typically offer technical support to help you with any issues.
  • Security: They implement security measures to protect your repository from unauthorized access.
  • Cost-Effectiveness: Hosting providers often offer different pricing plans to suit various needs, potentially making it more cost-effective than managing your own server.

1.5 Alternatives to SVN West

While SVN West is a good option, there are other SVN hosting providers and alternative version control systems:

  • Other SVN Hosting Providers: Assembla, Beanstalk, Perforce Helix, are examples.
  • Git (Distributed Version Control System – DVCS): Git is the most popular version control system today. Unlike SVN’s centralized model, Git is distributed, meaning each developer has a complete copy of the repository, including its history. Popular Git hosting providers include GitHub, GitLab, and Bitbucket.
  • Mercurial (DVCS): Mercurial is another distributed version control system similar to Git.

Choosing between SVN and Git (or Mercurial) depends on your project’s needs and your team’s preferences. Git is generally preferred for its flexibility and speed, especially for large, distributed teams. SVN can be a good choice for smaller teams or projects where a centralized model is preferred, or when transitioning from an existing SVN workflow.

2. Getting Started: Setting Up Your Environment

2.1 Creating an SVN West Account

  1. Visit the SVN West Website: Go to the SVN West website (you’ll need to find their official URL).
  2. Choose a Plan: Select a hosting plan that suits your needs. Consider factors like storage space, number of users, and features.
  3. Sign Up: Provide the necessary information (username, email, password, billing details) to create your account.
  4. Create a Repository: Once your account is set up, you’ll likely be guided through the process of creating your first SVN repository. You’ll need to choose a name for your repository.

2.2 Installing a Subversion Client

You need an SVN client to interact with your SVN West repository. Here are some popular options:

2.2.1 TortoiseSVN (Windows)

TortoiseSVN is a very popular, free, and open-source SVN client for Windows. It integrates directly with Windows Explorer, making it very user-friendly.

  1. Download: Download the TortoiseSVN installer from the official website (tortoisesvn.net).
  2. Install: Run the installer and follow the on-screen instructions. You may need to restart your computer after installation.
  3. Integration: After installation, you’ll see new TortoiseSVN options in the right-click context menu of Windows Explorer.

2.2.2 SmartSVN (Cross-Platform)

SmartSVN is a commercial SVN client that works on Windows, macOS, and Linux. It offers a more feature-rich interface than TortoiseSVN, but it’s not free (although a free trial is usually available).

  1. Download: Download the SmartSVN installer from the official website (smartsvn.com).
  2. Install: Run the installer and follow the instructions.
  3. License: You’ll need to obtain a license (or use the trial version).

2.2.3 Command-Line Client (Linux/macOS/Windows)

SVN also provides a command-line client that can be used on any operating system. This is a powerful option for experienced users who prefer working in the terminal.

  • Linux: Most Linux distributions have SVN pre-installed or available through their package manager (e.g., apt-get install subversion on Debian/Ubuntu, yum install subversion on Fedora/CentOS).
  • macOS: SVN is usually pre-installed on macOS. You can access it through the Terminal application. If it’s not installed, you can use Homebrew (brew install subversion).
  • Windows: You can download the command-line tools from the Apache Subversion website or use a package manager like Chocolatey (choco install svn).

2.2.4 Choosing the Right Client

  • TortoiseSVN: Best for beginners on Windows due to its ease of use and Explorer integration.
  • SmartSVN: Good for users who need a more advanced GUI client and are willing to pay for it.
  • Command-Line Client: Ideal for experienced users comfortable with the terminal, scripting, and automation.

2.3 Connecting to Your SVN West Repository

Once you have an SVN client installed, you need to connect to your SVN West repository. You’ll need the repository URL provided by SVN West. This URL will typically look something like this:

https://svn.svn-west.com/your-repository-name
or
svn://svn.svn-west.com/your-repository-name
or
svn+ssh://[email protected]/your-repository-name
The specific protocol (https, svn, or svn+ssh) will depend on how SVN West has configured their server and your account settings.

  • TortoiseSVN: Right-click in an empty folder where you want to create your working copy, and select “SVN Checkout…”. Paste the repository URL into the “URL of repository” field.
  • SmartSVN: Go to “Project” -> “Check Out…”. Enter the repository URL.

  • Command-Line: Use the svn checkout command:

    bash
    svn checkout https://svn.svn-west.com/your-repository-name my-working-copy
    (Replace my-working-copy with the desired name for your local working copy directory).

You’ll likely be prompted for your SVN West username and password. The client will then download a copy of the repository’s contents to your local machine (creating your working copy).

3. Core Concepts: Understanding the SVN Workflow

Before diving into specific commands, it’s essential to understand the fundamental concepts of SVN.

3.1 Repository

The repository is the central storage location for all your project’s files and their history. It’s hosted on the SVN West server. Think of it as the “master copy” of your project.

3.2 Working Copy

A working copy is a local copy of the repository’s files on your computer. You make changes to files within your working copy, and then commit those changes back to the repository. Multiple developers can have their own working copies, allowing them to work independently.

3.3 Trunk, Branches, and Tags

SVN uses a directory structure within the repository to organize different lines of development.

3.3.1 Trunk (Mainline Development)

The trunk directory typically represents the main line of development for your project. This is where the most stable and up-to-date code resides. New features are usually developed in branches and then merged back into the trunk.

3.3.2 Branches (Feature Development, Bug Fixes)

Branches are used to create separate lines of development, allowing you to work on new features or bug fixes without affecting the stability of the trunk. Once a feature is complete or a bug is fixed, the changes can be merged back into the trunk. Branches are typically created in a branches directory. For example:

/trunk
/branches
/feature-new-login
/bugfix-issue-123
/tags

3.3.3 Tags (Release Snapshots)

Tags are used to create snapshots of the repository at specific points in time, usually to mark releases (e.g., version 1.0, version 2.0). Tags are typically read-only; you don’t make changes directly to a tag. Tags are usually created in a tags directory. For example:

/trunk
/branches
/tags
/v1.0
/v1.1
/v2.0

3.4 Revisions

Every time you commit changes to the repository, SVN creates a new revision. Revisions are numbered sequentially (1, 2, 3, …). Each revision represents a specific state of the entire repository at a particular point in time.

3.5 Commits

A commit is the act of saving changes from your working copy to the repository. When you commit, you’re essentially creating a new revision. Commits should be atomic (all or nothing) and accompanied by a descriptive commit message explaining the changes.

3.6 Updates

An update is the process of synchronizing your working copy with the latest changes in the repository. When you update, your local files are updated to match the latest revision (or a specific revision you choose).

3.7 Conflicts

Conflicts occur when two or more developers have made changes to the same lines of a file, and SVN cannot automatically merge those changes. Conflicts need to be resolved manually by the developer.

3.8 The SVN Workflow Diagram

Here’s a simplified diagram illustrating the basic SVN workflow:

+-----------------+
| Repository |
| (SVN West Server)|
+-----------------+
^ |
| v
Commit Update
^ |
| v
+-----------------+ +-----------------+ +-----------------+
| Developer A | | Developer B | | Developer C |
| (Working Copy) | | (Working Copy) | | (Working Copy) |
+-----------------+ +-----------------+ +-----------------+
| | |
| Make Changes | Make Changes | Make Changes
| | |
+----------------------+----------------------+
Checkout (Initial)

  1. Checkout: Developers A, B, and C initially check out a working copy of the repository.
  2. Make Changes: Each developer works independently on their working copy, making changes to files.
  3. Update: Developers periodically update their working copies to get the latest changes from the repository.
  4. Commit: Developers commit their changes to the repository, creating new revisions.

4. Basic Operations: Working with Your Repository

Now, let’s cover the fundamental SVN commands you’ll use on a daily basis. We’ll provide examples using both TortoiseSVN (GUI) and the command-line client.

4.1 Checkout: Getting a Working Copy

As described earlier, checkout is the process of obtaining a working copy from the repository.

  • TortoiseSVN: Right-click in an empty folder -> “SVN Checkout…” -> Enter repository URL -> Click “OK”.

  • Command-Line:

    bash
    svn checkout <repository_url> <local_directory_name>
    Example:
    bash
    svn checkout https://svn.svn-west.com/myrepo myproject
    This will create a directory named myproject containing the working copy.

4.2 Update: Synchronizing Your Working Copy

Update brings your working copy up to date with the latest changes in the repository.

  • TortoiseSVN: Right-click on your working copy folder (or a specific file/folder within it) -> “SVN Update”.

  • Command-Line:

    bash
    svn update
    (Run this command from within your working copy directory). You can also update to a specific revision:

    bash
    svn update -r <revision_number>

4.3 Add: Adding New Files and Directories

When you create new files or directories within your working copy, you need to tell SVN to track them. This is done using the add command.

  • TortoiseSVN: Right-click on the new file or directory -> TortoiseSVN -> “Add”.

  • Command-Line:

    bash
    svn add <file_or_directory_name>
    Example:
    bash
    svn add newfile.txt
    svn add new_directory
    The add command schedules the file or directory for addition to the repository. It doesn’t actually add it to the repository until you commit.

4.4 Commit: Saving Changes to the Repository

Commit saves your local changes to the repository, creating a new revision.

  • TortoiseSVN: Right-click on your working copy folder (or a specific file/folder) -> “SVN Commit…”. You’ll be prompted to enter a commit message.

  • Command-Line:

    bash
    svn commit -m "Your commit message here"
    The -m option allows you to specify the commit message directly. If you omit -m, SVN will open a text editor for you to enter the message.

4.4.1 Writing Good Commit Messages

Commit messages are crucial for understanding the history of your project. Here are some best practices:

  • Be Descriptive: Explain what changes you made and why.
  • Be Concise: Keep the message relatively short, but informative.
  • Use Imperative Mood: Write as if you’re giving a command (e.g., “Fix bug in login form” instead of “Fixed bug in login form”).
  • Reference Issue Numbers: If your team uses an issue tracker, include the issue number in the commit message (e.g., “Fix #123: Login form validation error”).
  • Separate Summary and Body (Optional): For more complex changes, you can write a short summary line, followed by a blank line, and then a more detailed explanation.

4.5 Delete: Removing Files and Directories

To remove files or directories from the repository, you need to use the svn delete command. Simply deleting the file from your working copy won’t remove it from the repository.

  • TortoiseSVN: Right-click on the file or directory -> TortoiseSVN -> “Delete”.

  • Command-Line:

    bash
    svn delete <file_or_directory_name>
    Example:
    bash
    svn delete oldfile.txt
    svn delete unused_directory
    Like svn add, svn delete schedules the removal. The file or directory is not actually removed from the repository until you commit.

4.6 Move/Rename: Restructuring Your Project

To move or rename files or directories within the repository, use the svn move (or svn rename) command.

  • TortoiseSVN: Right-click on the file or directory -> TortoiseSVN -> “Rename…” (for renaming) or drag-and-drop the file/directory to its new location while holding down the right mouse button, then select “SVN Move versioned item(s) here”.

  • Command-Line:

    bash
    svn move <source> <destination>
    svn rename <old_name> <new_name> # Same as svn move
    Example:
    bash
    svn move file1.txt src/file1.txt
    svn rename old_directory new_directory
    Again, these changes are scheduled and require a commit to be applied to the repository.

4.7 Revert: Undoing Local Changes

If you’ve made changes to your working copy that you want to discard, you can use the svn revert command.

  • TortoiseSVN: Right-click on the file or directory -> TortoiseSVN -> “Revert…”.

  • Command-Line:

    bash
    svn revert <file_or_directory_name>
    Example:
    bash
    svn revert modified_file.txt
    This will restore the file to its last updated state from the repository. Be careful, as svn revert permanently discards your local changes.

4.8 Status: Checking the Status of Your Working Copy

The svn status command shows the status of files and directories in your working copy. It indicates which files have been modified, added, deleted, etc.

  • TortoiseSVN: Right-click on your working copy folder -> TortoiseSVN -> “Check for modifications”.

  • Command-Line:

    bash
    svn status

The output of svn status uses single-letter codes to indicate the status of each item:

  • (space): No modifications.
  • M: Modified.
  • A: Added.
  • D: Deleted.
  • ?: Not under version control.
  • !: Missing (deleted from the working copy, but still in the repository).
  • C: Conflict.
  • I: Ignored.

4.9 Ignoring Files and Directories (svn:ignore)

You often have files or directories in your working copy that you don’t want to be tracked by SVN (e.g., build artifacts, temporary files, IDE configuration files). You can tell SVN to ignore these using the svn:ignore property.

  • TortoiseSVN: Right-click on the folder where you want to set the ignore pattern -> TortoiseSVN -> Properties -> New -> “ignore” -> Enter the patterns (one per line) -> Click “OK”.

  • Command-Line:
    bash
    svn propset svn:ignore "pattern1\npattern2" .
    Replace .with the directory where you want to set the ignore property. Use the following patterns to match files/folders:

    • *: Wildcard, matches any characters.
    • ?: Matches a single character.
    • []: Matches a set of characters.

    Examples:
    *.log # Ignore all files ending with .log
    build/ # Ignore the build directory
    *.tmp # Ignore all .tmp
    [Tt]emp # Ignore file or folder name Temp or temp
    It’s common practice to set svn:ignore on the parent directory of the files/directories you want to ignore. You’ll need to commit the changes to the svn:ignore property.

5. Branching and Merging: Managing Parallel Development

Branching and merging are essential for managing parallel development in SVN.

5.1 Creating a Branch

Creating a branch is essentially making a copy of a part of the repository (usually the trunk) at a specific revision.

  • TortoiseSVN: Right-click on the directory you want to branch (e.g., the trunk directory) -> TortoiseSVN -> “Branch/tag…” -> In the “To URL” field, enter the URL for the new branch (e.g., https://svn.svn-west.com/myrepo/branches/my-new-branch) -> Click “OK”.

  • Command-Line:

    bash
    svn copy <source_url> <destination_url> -m "Creating branch my-new-branch"
    Example:
    bash
    svn copy https://svn.svn-west.com/myrepo/trunk https://svn.svn-west.com/myrepo/branches/my-new-branch -m "Creating branch for feature X"
    This creates a new branch named my-new-branch in the branches directory.

5.2 Switching Between Branches

To work on a branch, you need to “switch” your working copy to that branch.

  • TortoiseSVN: Right-click on your working copy folder -> TortoiseSVN -> “Switch…” -> Enter the URL of the branch you want to switch to -> Click “OK”.

  • Command-Line:

    bash
    svn switch <branch_url>
    Example:
    bash
    svn switch https://svn.svn-west.com/myrepo/branches/my-new-branch
    This updates your working copy to reflect the contents of the branch.

5.3 Merging Changes from a Branch to Trunk

Once you’ve finished working on a branch, you’ll want to merge the changes back into the trunk.

  • TortoiseSVN:

    1. Update your working copy of the trunk: Make sure your trunk working copy is up to date.
    2. Right-click on your trunk working copy folder -> TortoiseSVN -> “Merge…”.
    3. Select “Merge a range of revisions”.
    4. In the “URL to merge from” field, enter the URL of the branch you want to merge.
    5. Leave the “Revision range to merge” blank to merge all revisions.
    6. Click “Next” and follow the prompts.
    7. Test the merge thoroughly.
    8. Commit the merge.

  • Command-Line:

    1. Update trunk
    2. Switch to the trunk if not already.
    3. Use the below syntax.
      bash
      svn merge <branch_url>
      Example:
      bash
      svn update
      svn switch <trunk URL>
      svn merge https://svn.svn-west.com/myrepo/branches/my-new-branch
      This merges all changes from the branch into your working copy of the trunk. You’ll then need to commit the merge.

5.4 Merging Changes from Trunk to a Branch

Sometimes, you’ll want to “rebase” your branch by merging changes from the trunk into your branch. This keeps your branch up to date with the latest changes in the trunk and can help prevent conflicts when you eventually merge back into the trunk.

  • TortoiseSVN: The process is similar to merging from branch to trunk, but you switch the source and destination. Update your branch working copy, then merge from the trunk URL.

  • Command-Line:

    bash
    svn update
    svn switch <branch_url>
    svn merge <trunk_url>
    This merges changes from the trunk into your working copy of the branch. Commit the merge.

5.5 Handling Merge Conflicts

Conflicts can occur during merging when two or more developers have modified the same lines of a file.

5.5.1 Identifying Conflicts

SVN will indicate conflicts in the output of the svn update or svn merge command. Conflicted files will be marked with a “C” in the svn status output. SVN also creates several temporary files to help you resolve the conflict:

  • <filename>.mine: Your version of the file before the merge.
  • <filename>.<revision>: The version of the file from the repository before your changes.
  • <filename>.<revision>: The version of the file from the branch you’re merging.
  • <filename>: The file with conflict markers.

5.5.2 Resolving Conflicts Manually

Open the conflicted file (<filename>) in a text editor. You’ll see conflict markers that look like this:

“`
<<<<<<< .mine
Your changes here
=======
Changes from the other branch/revision here

.rXXXX
“`

You need to manually edit the file to resolve the conflict. Choose which changes to keep, or combine them, and then remove the conflict markers.

5.5.3 Using Merge Tools

TortoiseSVN and other SVN clients often provide built-in merge tools or integrate with external merge tools (like KDiff3, Beyond Compare, or Araxis Merge) to help you visualize and resolve conflicts more easily.

After resolving the conflict, you need to tell SVN that the conflict is resolved:

  • TortoiseSVN: Right-click on the conflicted file -> TortoiseSVN -> “Resolved…”.

  • Command-Line:

    bash
    svn resolved <filename>

Then, commit the changes.

5.6 Best Practices for Branching and Merging

  • Keep Branches Short-Lived: The longer a branch lives, the more likely it is to diverge from the trunk and cause merge conflicts.
  • Merge Frequently: Merge changes from the trunk into your branch regularly to keep it up to date.
  • Test Thoroughly: Always test your code thoroughly after merging.
  • Communicate: Communicate with your team about your branching and merging strategy.

6. Tagging: Creating Release Snapshots

Tags are used to create snapshots of the repository at a specific point in time, typically for releases.

6.1 Creating a Tag

Creating a tag is similar to creating a branch; it’s essentially a copy.

  • TortoiseSVN: Right-click on the directory you want to tag (usually the trunk or a branch) -> TortoiseSVN -> “Branch/tag…” -> In the “To URL” field, enter the URL for the new tag (e.g., https://svn.svn-west.com/myrepo/tags/v1.0) -> Click “OK”.

  • Command-Line:

    bash
    svn copy <source_url> <destination_url> -m "Creating tag v1.0"
    Example:
    bash
    svn copy https://svn.svn-west.com/myrepo/trunk https://svn.svn-west.com/myrepo/tags/v1.0 -m "Creating tag for release 1.0"

6.2 Checking Out a Specific Tag

You can check out a specific tag to get a working copy of the project at that point in time. The process is the same as checking out the trunk or a branch; just use the tag’s URL.

  • TortoiseSVN: Right-click in an empty folder -> “SVN Checkout…” -> Enter the tag URL -> Click “OK”.

  • Command-Line:

    bash
    svn checkout <tag_url> <local_directory_name>
    Example:
    bash
    svn checkout https://svn.svn-west.com/myrepo/tags/v1.0 myproject-v1.0

Remember that tags are typically read-only. If you need to make changes, you should create a branch from the tag.

7. Inspecting History: Exploring the Repository’s Past

SVN provides powerful tools for inspecting the history of your project.

7.1 Log: Viewing Commit History

The svn log command shows the commit history of a file or directory.

  • TortoiseSVN: Right-click on a file or directory -> TortoiseSVN -> “Show log”.

  • Command-Line:

    bash
    svn log
    (Shows the log for the current directory and its subdirectories).

    bash
    svn log <file_or_directory_name>
    (Shows the log for a specific file or directory).

    bash
    svn log -r <revision_number>
    (Shows the log for a specific revision).

    bash
    svn log -r <start_revision>:<end_revision>
    (Shows the log for a range of revisions).

    bash
    svn log -v #Verbose

The log output shows the revision number, author, date, and commit message for each commit.

7.2 Diff: Comparing Revisions

The svn diff command shows the differences between revisions.

  • TortoiseSVN: Right-click on a file or directory -> TortoiseSVN -> “Diff with previous version” (to compare with the previous revision). You can also select two revisions in the log window and choose “Compare revisions”.
  • **Command-Line

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top