CEF Forum

For example:

when we developed features, we made patch1, patch2, patch3.
Now we are updating chromium to a new version, patches possibly cannot be applied.
Then we might need following steps:
1. checkout chromium code to the commit before patch1, apply patch1 and resolve conflics, and remake patch1.
2. temporarily commit patch1, apply patch2 and resolve conflics, and remake patch2.
3. temporarily commit patch2, apply patch3 and resolve conflics, and remake patch3.
...
(additionally, every step should do CEF translator for api hash, should compile all code and run tests to check the feature for that patch, ...)

That costs too long time... How does CEF do this work?

We use scripts for updating patches. See https://bitbucket.org/chromiumembedded/ ... mUpdate.md

You could also avoid checking in changes to auto-generated files and instead run the translator tool before building.