Am Sa., 8. Mai 2021 um 03:08 Uhr schrieb Julius Werner <jwer...@chromium.org >:
> I understand that you might like to have both [features and stability] but > I think that's just fundamentally impossible -- big new features just tend > to require deep, invasive changes. +1 > I think we could encourage that, I don't think it's really something > you can make a hard requirement. spatches just don't work well for all > kinds of API changes. Starting this as a sort of "experiment" like you > suggested to see how it goes sounds like a good idea. > This is why my proposed documentation change ( https://review.coreboot.org/c/coreboot/+/52576/1/Documentation/getting_started/gerrit_guidelines.md#335) states: "Providing a script or a [coccinelle]( https://coccinelle.gitlabpages.inria.fr/website/) semantic patch to automate this step is extra helpful, so consider doing that if possible." The only "shall do" request is that there's _some_ documentation about what has been going on, and that can be as short as "commit abc replaced foo(a,b) with bar(b,a)." Do I need to emphasize the "if possible" part some more? Patrick -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
_______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
