On Fri, May 08, 2020 at 09:39:58AM -0600, Ken Dreyer wrote: > In Ceph we do this at a slightly different point of time. We use > "rdopkg tag-patches" to save each of the "patches" refs that we've > translated into patch series in dist-git. Each Git tag is the NVR of > the package. > > We rebase and force-push our "patches" branches frequently, so a > patches branch is one "history", and dist-git becomes a "history of > histories". > > It's critical to have this flexibility + auditability so we can move > fast and still go back and reproduce everything. > How do you backport fixes? Do apply the fixes directly to dist-git? Or do you apply the fixes to a corresponding patches branch that you occur to have around till needed (e.g. till the hitorical code is supported) for the purpose of backporting? -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
