Re: Why does acessing logs using "-r HEAD" doesn't provide results?
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@COMMITTED" > > > 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! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Why does acessing logs using "-r HEAD" doesn't provide results?
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@COMMITTED"
> >
> >
> > 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»
