Rework and fix HGSourceCodeManager >> #revisionLogOf:...directory:module:`
This commit changes the logic in two ways:
1. #newestRevision is now the newest revision in the branch that
*contains* given file (not necesarily modidfes it). If there are
multiple heads in that branch, pretty much random one is returned.
This changes old behavior and therefore this commit updates
tests.
2. If a specific single revision is requested, i.e., both from and to revisions
are the same, revision log with that single revision is returned
no matter whether it modifies the file or even contains that file
at all. This is essentially a workaround to fix issue #305.
Moreover, this commit simplifies the code a lot by delegating all the
changeset searching and filtering to mercurial using revset expressions.
See https://swing.fit.cvut.cz/projects/stx-jv/ticket/305#comment:3
"{ Package: 'stx:libscm/git' }"
SharedPool subclass:#GitSubmoduleUpdateType
instanceVariableNames:''
classVariableNames:'SUBMODULE_UPDATE_DEFAULT SUBMODULE_UPDATE_CHECKOUT
SUBMODULE_UPDATE_REBASE SUBMODULE_UPDATE_MERGE
SUBMODULE_UPDATE_NONE'
poolDictionaries:''
category:'SCM-Git-Core-Internal-Constants'
!
!GitSubmoduleUpdateType class methodsFor:'initialization'!
initialize
SUBMODULE_UPDATE_DEFAULT := -1.
SUBMODULE_UPDATE_CHECKOUT := 0.
SUBMODULE_UPDATE_REBASE := 1.
SUBMODULE_UPDATE_MERGE := 2.
SUBMODULE_UPDATE_NONE := 3.
! !
!GitSubmoduleUpdateType class methodsFor:'constants'!
SUBMODULE_UPDATE_CHECKOUT
^SUBMODULE_UPDATE_CHECKOUT
!
SUBMODULE_UPDATE_DEFAULT
^SUBMODULE_UPDATE_DEFAULT
!
SUBMODULE_UPDATE_MERGE
^SUBMODULE_UPDATE_MERGE
!
SUBMODULE_UPDATE_NONE
^SUBMODULE_UPDATE_NONE
!
SUBMODULE_UPDATE_REBASE
^SUBMODULE_UPDATE_REBASE
! !
!GitSubmoduleUpdateType class methodsFor:'documentation'!
version_GIT
"Never, ever change this method. Ask JV or CG why"
^thisContext method mclass theNonMetaclass instVarNamed: #revision
!
version_SVN
^ '$Id$'
! !
GitSubmoduleUpdateType initialize!