Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • 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 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
  • gitlab-ce
  • lib
  • gitlab
  • git
  • rugged_impl
  • ref.rb
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Bring back Rugged implementation of find_commit · fb6a4e21
    Stan Hu authored Feb 21, 2019
    This brings back some of the changes in
    https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20339.
    
    For users using Gitaly on top of NFS, accessing the Git data directly
    via Rugged is more performant than Gitaly. This merge request introduces
    the feature flag `rugged_find_commit` to activate Rugged paths.
    
    There are also Rake tasks `gitlab:features:enable_rugged` and
    `gitlab:features:disable_rugged` to enable/disable these feature
    flags altogether.
    
    Part of four Rugged changes identified in
    https://gitlab.com/gitlab-org/gitlab-ce/issues/57317.
    fb6a4e21
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7