[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn log behaviour

From: Ryan Schmidt <subversion-2011a_at_ryandesign.com>
Date: Mon, 14 Feb 2011 01:59:34 -0600

On Feb 14, 2011, at 01:57, Alex Bligh wrote:

> On 14 February 2011 01:10:08 -0600 Ryan Schmidt wrote:
>>> If I do "svn log ." in a directory, it does not list all changes made to
>>> all files in that directory (as shown up "svn log <filename>"). I've
>>> pasted an example at:
>>> http://pastebin.com/SFYDtkBk
>>> where r12062 does not show up in "svn log .", but does on the changed
>>> file.
>>> svn diff . does the expected, and the file is not in svn:ignore.
>>> Is this deliberate and how do I get a recursive list of logs?
>> Is the directory up to date? Try "svn up" first. Otherwise you'll only
>> get logs up to the revision of the directory (shown with "svn info").
> Yes, the directory is up to date. In fact all changes were made in that
> directory (not on another machine).

Just because you committed the changes from that directory does not mean it is up to date. In fact, usually, after committing changes, your working copy has mixed revisions and is therefore not up to date. Please verify whether running "svn up" first fixes the problem.
Received on 2011-02-14 09:00:18 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.