Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S StreamChain Prototype
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • zistvan-public
  • StreamChain Prototype
  • Repository
  • streamchain
  • common
  • configtx
  • configmap.go
Find file BlameHistoryPermalink
  • Jason Yellick's avatar
    [FAB-2511] Make configtx sequence explicit · 2a6a7b57
    Jason Yellick authored Feb 27, 2017
    https://jira.hyperledger.org/browse/FAB-2511
    
    
    
    The previous non-MVCC configuration system required that the modified
    version numbers of the configuration elements be equal to the global
    configuration sequence lock.
    
    This makes the global sequence explicit, while allowing the individual
    elements to move (or not move) their version numbers locally.  This
    finally enables the partial update functionality advertised in FAB-1880.
    
    Change-Id: Ic2f554b864e91435a8812d56eb8247cc1fa33720
    Signed-off-by: default avatarJason Yellick <jyellick@us.ibm.com>
    2a6a7b57