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

Re: Why does acessing logs using "-r HEAD" doesn't provide results?

From: Lorenz <lorenznl_at_yahoo.com>
Date: Tue, 19 May 2020 05:22:31 +0000

Thorsten Schöning wrote:

>Hi all,
>I'm having trouble understanding a problem with comparing paths in
>WebSVN: Comparing two paths uses HEAD as revision specifier by default
>and works in one setup and doesn't in another. The root cause is that
>accessing the history of the repo simply doesn't provide any results
>when used like the following:
>> C:\[...]>svn log -r HEAD C:\[...]\trunk --xml --limit 1
>> <?xml version="1.0" encoding="UTF-8"?>
>> <log>
>> </log>
>Using the concrete revision number the working copy is in or some
>different keyword works:
>> C:\[...]>svn log -r COMMITTED C:\[...]\trunk --xml --limit 1
>> <?xml version="1.0" encoding="UTF-8"?>
>> <log>
>> <logentry
>> revision="667">
>> </logentry>
>> </log>
>So why does HEAD doesn't provide any details? Thanks!

though Daniel mentions it already in the first third of his first
sentence, I wanted to point out the most likely reason more

Because --limit relates to overall repository revisions, not path
relates revisions:

You first example looks exactly for the HEAD revision of the
repository. If you path was not touched by this revision, there is no
log regarding this path and revision to return.

Your second example on the other hand explicitly asks for the log
message of the last revision the given path was touched.

Received on 2020-05-19 07:24:05 CEST

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