{"id":290,"date":"2026-10-13T09:21:06","date_gmt":"2026-10-13T09:21:06","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2010\/11\/26\/examining-history-in-subversion\/"},"modified":"2026-10-13T09:21:06","modified_gmt":"2026-10-13T09:21:06","slug":"examining-history-in-subversion","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/examining-history-in-subversion\/","title":{"rendered":"How to Examine History in Subversion (SVN) with log, diff, cat, and list"},"content":{"rendered":"\n

Originally published on 2010-11-26; fully revised and updated.<\/em><\/p>\n\n\n\n

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

What each SVN history command is best at<\/h2>\n\n\n\n

Subversion provides multiple history commands, each optimized for a different level of detail. In practice, you will often use them together.<\/p>\n\n\n\n

Command<\/th>Best for<\/th>Level of detail<\/th>Typical output<\/th><\/tr><\/thead>
svn log<\/code><\/td>Finding relevant revisions, author, date, and commit messages<\/td>High-level revision metadata<\/td>Revision entries and changed paths (with verbose mode)<\/td><\/tr>
svn diff<\/code><\/td>Inspecting exact line-by-line code changes<\/td>Line-level patch detail<\/td>Added\/removed\/modified lines between revisions<\/td><\/tr>
svn cat<\/code><\/td>Viewing file contents exactly as they were in a past revision<\/td>Full file content snapshot<\/td>File text printed to standard output<\/td><\/tr>
svn list<\/code><\/td>Checking directory contents at a specific revision<\/td>Directory-level view<\/td>Names of files and subdirectories for that revision<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Workflow: trace a problem back to a specific revision<\/h2>\n\n\n\n

A reliable way to investigate historical changes is to start broad with logs, then drill down with diffs and content retrieval.<\/p>\n\n\n\n

\nflowchart TD\n    A[Start with a file or directory] --> B[Run svn log]\n    B --> C{Need line level details}\n    C -- yes --> D[Run svn diff on candidate revision]\n    C -- no --> E{Need exact old file content}\n    D --> E\n    E -- yes --> F[Run svn cat at that revision]\n    E -- no --> G{Need directory view at revision}\n    F --> G\n    G -- yes --> H[Run svn list at that revision]\n    G -- no --> I[Record revision and findings]\n    H --> I\n<\/pre>\n\n\n\n
Command examples you can reuse<\/h2>\n\n\n\n
Use these examples as templates and replace paths, revision numbers, and URLs with values from your repository.<\/p>\n\n\n\n
1) View commit history with svn log<\/h3>\n\n\n
svn log -l 10\nsvn log path\/to\/file.txt\nsvn log -r 120 path\/to\/file.txt\nsvn log --verbose -r 120 path\/to\/project<\/code><\/span><\/pre>\n\n\n
Use svn log<\/code> first to identify candidate revisions before deeper inspection.<\/p>\n\n\n\n
2) Inspect line changes with svn diff<\/h3>\n\n\n
svn diff -c 120 path\/to\/file.txt\nsvn diff -r 119:120 path\/to\/file.txt<\/code><\/span><\/pre>\n\n\n
Use svn diff<\/code> when you need the precise code-level change, not just commit metadata.<\/p>\n\n\n\n
3) Retrieve historical file content with svn cat<\/h3>\n\n\n
svn cat -r 120<\/span> path\/to\/file.txt\nsvn cat -r 120<\/span> https:\/\/svn.example.com\/repo\/trunk\/path\/to\/file.txt<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
svn cat<\/code> is useful when you need to review an old file quickly without switching your working copy.<\/p>\n\n\n\n
4) List directory contents for a revision with svn list<\/h3>\n\n\n
svn list<\/span> -r 120<\/span> path\/to\/directory\nsvn list<\/span> -r 120<\/span> https:\/\/svn.example.com\/repo\/trunk\/<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Use svn list<\/code> when you need to verify whether a file existed in a directory at a given revision.<\/p>\n\n\n\n
Best practices and common pitfalls<\/h2>\n\n\n\n
  • Start with svn log<\/code> to narrow scope, then use svn diff<\/code> for exact changes.<\/li>
  • Use file or subdirectory paths to reduce noisy history from unrelated parts of the repository.<\/li>
  • Remember that SVN revision numbers are repository-wide, not per-file counters.<\/li>
  • If output is empty, verify that the path existed at that revision and that you have access rights.<\/li>
  • Record revision numbers in incident or change notes so later audits are repeatable.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
    Subversion keeps a complete change history, but getting useful answers depends on choosing the right command. This guide shows when and how to use svn log, svn diff, svn cat, and svn list with practical examples.<\/p>\n","protected":false},"author":1,"featured_media":4339,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[23],"tags":[4044,4050,4046,1122,4047,2624,3113,593,394,4045,4048,4049,213],"class_list":["post-290","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-svnsubversion","tag-examin","tag-examin-svn-history","tag-examining-history-in-subversion","tag-guide","tag-historical-data","tag-history","tag-how-to","tag-process","tag-subversion","tag-subversion-history","tag-svn-commit-history","tag-svn-history-examining-command","tag-tutorial"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=290"}],"version-history":[{"count":6,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/290\/revisions"}],"predecessor-version":[{"id":79126,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/290\/revisions\/79126"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4339"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}