I can't imagine you could do much better than maintaining your own V8 branch(es) and just merging V8 changes when you want to upgrade V8. Otherwise you'll have to reinvent some git functionality -- there's no way to avoid merging your changes with V8 changes. If you're willing to go down this path, adding your own versioning scheme on top of V8's shouldn't be daunting.
On Tuesday, October 27, 2020 at 4:18:04 PM UTC-4 pranayg...@gmail.com wrote: > Hi, > > I am currently playing with different builtins in V8. Trying to add some > functionality in-order to do taint tracking > <https://www.andrew.cmu.edu/user/liminjia/research/papers/chromium-taint-ndss2015.pdf>. > > I want to come-up with an efficient way to version-control and integrate my > changes within the V8 codebase. > > Say I changed the file* v8/src/builtins/builtins-string.cc*. I want to be > able to keep the changed file in my own git repo and automatically > integrate it during the build process. > > I understand the DEPS > <https://chromium.googlesource.com/chromium/src/+/master/buildtools/checkdeps/README.md>file > > might help me with this, but I'm not sure if this is the right direction. > > Can I get some pointers? > Much appreciated :) > > Thanks > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/f94a70c8-a456-4716-a5c5-0522dfe01a1cn%40googlegroups.com.
