I think we should prototype this as an add-on that keeps track of patch files and uses a registered chrome.manifest file to override any patched files. I'm not sure we should build a fully-featured "live" VCS into default Firefox builds.
I don't think it should be a "fully featured" VCS - just a linear set of changes, and the ability to roll them back. We don't need anything network-distributed or changeset merging or anything, just the ability to roll changes back.
omni.jar exists to address performance concerns, switching to a VCS would regress that. This would be fine to experiment with as an addon, but I don't think it's realistic to make this change in Firefox until a lot more work has been done.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.