How to Examine History in Subversion (SVN) with log, diff, cat, and list

Originally published on 2010-11-26; fully revised and updated.

If you work with Subversion, history inspection is how you answer core operational questions quickly: what changed, who changed it, and when it changed. This article helps developers, release engineers, and support teams use SVN history commands effectively, with a practical workflow and reusable command examples.

What each SVN history command is best at

Subversion provides multiple history commands, each optimized for a different level of detail. In practice, you will often use them together.

Workflow: trace a problem back to a specific revision

A reliable way to investigate historical changes is to start broad with logs, then drill down with diffs and content retrieval.

flowchart TD
    A[Start with a file or directory] --> B[Run svn log]
    B --> C{Need line level details}
    C -- yes --> D[Run svn diff on candidate revision]
    C -- no --> E{Need exact old file content}
    D --> E
    E -- yes --> F[Run svn cat at that revision]
    E -- no --> G{Need directory view at revision}
    F --> G
    G -- yes --> H[Run svn list at that revision]
    G -- no --> I[Record revision and findings]
    H --> I

Command examples you can reuse

Use these examples as templates and replace paths, revision numbers, and URLs with values from your repository.

1) View commit history with svn log

svn log -l 10
svn log path/to/file.txt
svn log -r 120 path/to/file.txt
svn log --verbose -r 120 path/to/project

Use svn log first to identify candidate revisions before deeper inspection.

2) Inspect line changes with svn diff

svn diff -c 120 path/to/file.txt
svn diff -r 119:120 path/to/file.txt

Use svn diff when you need the precise code-level change, not just commit metadata.

3) Retrieve historical file content with svn cat

svn cat -r 120 path/to/file.txt
svn cat -r 120 https://svn.example.com/repo/trunk/path/to/file.txtCode language: JavaScript (javascript)

svn cat is useful when you need to review an old file quickly without switching your working copy.

4) List directory contents for a revision with svn list

svn list -r 120 path/to/directory
svn list -r 120 https://svn.example.com/repo/trunk/Code language: PHP (php)

Use svn list when you need to verify whether a file existed in a directory at a given revision.

Best practices and common pitfalls

• Start with svn log to narrow scope, then use svn diff for exact changes.
• Use file or subdirectory paths to reduce noisy history from unrelated parts of the repository.
• Remember that SVN revision numbers are repository-wide, not per-file counters.
• If output is empty, verify that the path existed at that revision and that you have access rights.
• Record revision numbers in incident or change notes so later audits are repeatable.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.