From: Don Zickus on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_6805...
There is a long run-on sentence here. Can we break it up? One suggestion
(starting at 'Keeping the process......upstream merges only'):
""
Rebasing from time to time, helps reduce the clutter of the extra changes on
top of upstream and future merge conflicts. This periodic rebase addresses
the needs of the Fedora community's desire to separate upstream from Fedora
specific changes, helps keep it clear what patches changed in the final form
upstream, and what a Fedora specific patch looks like currently as opposed to
split across various conflict patches.
While rebasing has a negative effect on developer contribution, we believe
saving the rebase for the end of release cycle allows for minimal developer
contribution disruption while gaining the above advantages.
This process is open to feedback for improvements.
""
The spirit of the above is to lay out our reasons for performing a developer
impacting rebase. And then acknowledging that we understand this negatively
impacts developers. Followed by our desire to continue to evolve this
process.
Feel free to re-word/write my suggestion. :-)
Thoughts?