Hello, In article <CAFJ3QWKkzdEXjkLB=g9R7uJRxXse+hCpcfru6Dza+AVo=a-...@mail.gmail.com> guillaume.brune...@gmail.com writes:
> Hello, > > The command svn log -r BASE:HEAD . doesn't behave as I expect it to. > According to svn help log: > > Show the log messages for any incoming changes to foo.c during the > next 'svn update': > svn log -r BASE:HEAD foo.c This help message seems innacurate. 'svn log -r BASE:HEAD' shows log messages from "BASE" revision to "HEAD" revision on foo.c including both revisions, where "BASE" is the revision number of an item in working copy and "HEAD" is the latest(or "youngest") revision in the repository[1]. [1] Version Control with Subversion (Nightly Build) Chapter 3. Advanced Topics > Revision Specifiers > Revision Keywords http://svnbook.red-bean.com/nightly/en/svn.tour.revs.specifiers.html#svn.tour.revs.keywords > Yet on my machine I have the following behavior: > > > > svn up > Updating '.': > At revision 103730. > > svn log -r BASE:HEAD . > ------------------------------------------------------------------------ > r103730 | guillaumeb | 2021-06-01 09:35:24 +0200 (Tue, 01 Jun 2021) | 1 line > some commit message > ------------------------------------------------------------------------ > > svn up > Updating '.': > At revision 103730. > > > So svn log -r BASE:HEAD reported a log message for a change that was > already taken into account. > Is that a bug in svn or am I misunderstanding something? I would have > expected an empty result, given that there was no incoming change > during the next svn up. In this case, both of "BASE" and "HEAD" revisions are 103730, so it is equivalent to 'svn log -r 103730:103730', and in r103730, there is some changes in '.'. That is why it showed the log message. Cheers, -- Yasuhito FUTATSUKI <futat...@yf.bsdclub.org>
