Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • mercurial-devel mercurial-devel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • mercurialmercurial
  • mercurial-develmercurial-devel
  • Merge requests
  • !524

rust-changelog: introducing ChangelogEntry, a unique handle to access all data

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Georges Racinet requested to merge topic/default/rust-cl-entry into branch/default Mar 30, 2023
  • Overview 14
  • Commits 6
  • Pipelines 4
  • Changes 2

Everything should be explained in changeset descriptions.

Further notes:

  • there are no consumers of data_for_rev in the entire Mercurial code base
  • backwards compatibility is maintained.
  • my current experimental RHGitaly implementation uses the new ChangelogEntry and passes all tests against this topic (gitaly-comparison is the job for functional tests)
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: topic/default/rust-cl-entry