SubWCRev determines wrong version

[Tobias Knauss]

If you create a branch, switch to that branch and compile it, then SubWCRev takes the revision number of the source revision of that branch, but not of the branch itself.
Please fix this, so that SubWCRev takes the correct revision number of the branch.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3284657

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Stefan Küng]

On 10.08.2017 13:19, Tobias Knauss wrote:
> If you create a branch, switch to that branch and compile it, then
> SubWCRev takes the revision number of the source revision of that
> branch, but not of the branch itself. Please fix this, so that
> SubWCRev takes the correct revision number of the branch.

by default, SubWCRev only takes the last-committed-revision of files
into account. When you create a branch and don't commit any changes to
that branch, all files still have the same last-committed-revision of
the source.
You can pass -f to tell SubWCRev to also use the last-committed-revision
of folders, which then (if called for the root of the branch) includes
the branch revision.

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3284886

[Tobias Knauss]

If you create a branch, switch to that branch and compile it, then SubWCRev takes the revision number of the source revision of that branch, but not of the branch itself.
Please fix this, so that SubWCRev takes the correct revision number of the branch.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3286365

[Stefan Küng]

Before posting a second time, please read the answers to your first post:
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3284886

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------

http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3286636

[peter.l...@gmail.com]

Further to my previous message still pending review, had a homer moment and realised we'd had it working by dumb luck all these times. The problem for us was caused by us having not specified the root folder as the working folder and the last few commits were made in a different folder thus it didn't pick them up even with the -f option. Doh!

[peter.l...@gmail.com]

On Monday, 14 August 2017 21:31:28 UTC+1, Stefan wrote:

I'm experience the same problem, I was on 1.10, but upgraded to 1.11.

My steps to reproduce is:
1) Create Branch
2) More commits get made to branch from 1)
3) Branch gets tagged.
4) Building the branch, using SubWCRev with 3 params working dir, source file, destination file.

Result it ignores the last few commits, for example just now it output 11934 but yet there were 7 commits after that (11938, 11939, 11942 etc..) all of which made changes to files not folders.

We've been doing this same process for several years and it's only within the last year that we've noticed this happening.