Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
wayland
wayland
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 97
    • Issues 97
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 30
    • Merge Requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • waylandwayland
  • Issues
  • #49

Closed
Open
Created Jul 02, 2018 by Ongy@Ongy

Migrate merge requests to gitlab

As you are clearly aware, since you are on this shiny platform, wayland moved to gitlab, from the cgit/patchwork setup.

But the mailing list is still the main way of communication. Both for general discussion and development, even though gitlab provides features intended for the dev part.

The last information I could find on the [mailing list] (https://lists.freedesktop.org/archives/wayland-devel/2018-May/038110.html) is that there's two unsolved questions:

  1. How to achieve linear history
  2. How to add the R-b/A-b tags (S-b should be easy)

Since patches on the ml tend to be forgotten into oblivion unless bumped and the SNR on that list is horrible, I think it's reasonable to try and speed up the migration.


For the first point, I'm honestly confused why it's even a goal. It activly tries to reduce the pretty history graphs git generates into a single boring stack.

With MR-commits, the git history would provide a nice grouping of MRs and the actual commit message can be used for further information (e.g. back-link to the gitlab discussion, and the R-b/A-b tags could be shoehorned into that), but:

For the second point, I propose to use git notes, they are intended to amend commits with futher information without touching the commit itself.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None