Svn log - svn: '.' is not a working copy

svn repository logging working-copy
Filipe Pinheiro picture Filipe Pinheiro · Apr 28, 2010 · Viewed 7k times · Source

I'm getting "svn: '.' is not a working copy" when i use the svn log command.

I know that i need a working copy for the log command to work but can this be done directly on a repository?

My goal is to display the information (change history) of a repository. I think updating the working copy whenever i need the log information is not a good solution.

Is there an alternative solution to this or updating a working copy every time i need to log is the only way to go?

Thanks in advance.

Answer

Matt Bridges picture Matt Bridges · Apr 28, 2010

Try svn log [repository_url]

That will get the log of a particular repository rather than the local, checked-out repository.

See this documentation.

Related questions

How do I move a single folder from one Subversion repository to another repository?

I have a "docs" folder in a Subversion repository named "project". I've come to the conclusion that it should really be kept under a separate Subversion repository named "project_docs". I'd like to move the "docs" folder (and all of …

Read More
How to list all files in a remote SVN repository?

I access a large remote SVN repository. Since I usually only need a tiny subset of its content I did a "sparse checkout": svn checkout --depth empty svn+ssh://... src Whenever I need a folder from the repository I can …

Read More
SVN Synchronize vs Update to Head (subclipse)

I'm fairly new to both Subversion and Subclipse and am seeing some issues that lead me to believe there is a difference between updating to head, and synchronizing. Specifically I find that when I try to revert (using the subclipse …

Read More