Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 124
    • Merge requests 124
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Repository

Switch branch/tag
  • slapos
  • component
  • coreutils
  • buildout.cfg
Find file BlameHistoryPermalink
  • Carlos Ramos Carreño's avatar
    Fix patches from Github · 66c1fc8c
    Carlos Ramos Carreño authored Sep 21, 2024
    Several components use patches directly from Github.
    Unfortunately, Github changes the number of characters displayed for the
    commits in index lines depending on the size of the repository.
    That means, that the content of these patches may change, invalidating
    the MD5.
    
    By using the `?full_index=1` param
    (https://github.com/orgs/community/discussions/46034#discussioncomment-4846112)
    we can request that these patches include the full names of the commits,
    thus preventing future changes.
    
    See merge request !1645
    66c1fc8c

Replace buildout.cfg

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7