[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: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sun, 24 May 2020 22:03:14 +0000

Thorsten Schöning wrote on Sun, 24 May 2020 18:18 +0200:
> Guten Tag Daniel Shahaf,
> am Dienstag, 19. Mai 2020 um 19:17 schrieben Sie:
>
> > That would depend on what log message(s) you're trying to fetch, which
> > you haven't told us.
>
> I'm interested in the most recent one for a given path available in
> the repo, that's why HEAD has been used in the past I guess. Users can
> either provide a concret revision or not, in the latter case HEAD is
> assumed currently and didn't provide results sometimes.
>
> Additionally, things need to work by accessing the repo directly,
> without a local working copy. I've tried COMMITTED with a local
> working copy and that succeeded, but WebSVN is sometimes accessing the
> repo directly and that fails:
>
> > C:\Users\tschoening>"C:/Program Files/CollabNet/Subversion Client\svn" --non-interactive --config-dir /tmp/websvn log --xml --limit 1 -r COMMITTED:COMMITTED "file:///C:/[...]/trunk/keywords.txt_at_COMMITTED"
> > <?xml version="1.0" encoding="UTF-8"?>
> > <log>
> > svn: E195002: PREV, BASE, or COMMITTED revision keywords are invalid for URL
>
> So in the end, I simply need a keyword which always provides the most
> recent log history of some path in the repo. Thanks!

It's not a keyword, but I think it's what you want:

«svn log -r HEAD:0 --limit=1 -- ${TARGET}@HEAD»
Received on 2020-05-25 00:03:24 CEST

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