naiveproxy

mirror of https://github.com/klzgrad/naiveproxy.git synced 2024-11-28 00:06:09 +03:00

History

klzgrad 19bc836227 Import chromium-63.0.3239.132		2018-01-29 00:30:36 +08:00
..
0000-build.patch	Import chromium-63.0.3239.132	2018-01-29 00:30:36 +08:00
0001-simd.patch	Import chromium-63.0.3239.132	2018-01-29 00:30:36 +08:00
0002-uninitializedcheck.patch	Import chromium-63.0.3239.132	2018-01-29 00:30:36 +08:00
0003-use-defines-for-inffast.patch	Import chromium-63.0.3239.132	2018-01-29 00:30:36 +08:00
0004-neon-inffast.patch	Import chromium-63.0.3239.132	2018-01-29 00:30:36 +08:00
0005-adler32-simd.patch	Import chromium-63.0.3239.132	2018-01-29 00:30:36 +08:00
README	Import chromium-63.0.3239.132	2018-01-29 00:30:36 +08:00

README

== Patches applied on top of zlib ==

 - 0000-build.patch: changes from the upstream version, mostly related to the
   build.
 - 0001-simd.patch: integrate Intel SIMD optimizations from
   https://github.com/jtkukunas/zlib/

== Procedure to create a patch file ==

  Assuming you are working in a new feature branch:
 - git format-patch master --stdout > foo.patch # where naming follows a growing
                                                # number plus patch description.
 - git add foo.patch
 - git commit -a -m "Local patch."
 - git rebase -i HEAD~2 # Squashing the second commit

  As patches created in this way will feature a ChangeLog, there is no longer
the need to append this file with a description of what the patch does. This
should help to solve frequent conflicts in pending new patches on
Chromium's zlib.

  The plan for the near future is to insulate better the platform specific
changes to easy updates with new releases of zlib.

  Ideally local changes should have a merge request featured in either:
 - canonical zlib: https://github.com/madler/zlib/
 - zlib-ng: https://github.com/Dead2/zlib-ng