mirror of
https://github.com/unicode-org/icu.git
synced 2025-04-05 21:45:37 +00:00
ICU-11318 Adding instructions and todo items to double-conversion UPDATING.md
X-SVN-Rev: 40933
This commit is contained in:
parent
05b4908921
commit
cb99bc0c44
1 changed files with 10 additions and 2 deletions
12
vendor/double-conversion/UPDATING.md
vendored
12
vendor/double-conversion/UPDATING.md
vendored
|
@ -1,7 +1,7 @@
|
|||
© 2016 and later: Unicode, Inc. and others.
|
||||
License & terms of use: http://www.unicode.org/copyright.html
|
||||
|
||||
## Updating double-conversion from Github to ICU4C
|
||||
## Updating double-conversion from Github to Vendor
|
||||
|
||||
Go to https://github.com/google/double-conversion/releases/latest/ to determine the latest version number; for the examples below, suppose it is `v3.0.0`.
|
||||
|
||||
|
@ -9,4 +9,12 @@ Run `pull-from-upstream.sh` as below:
|
|||
|
||||
./pull-from-upstream.sh v3.0.0
|
||||
|
||||
Further instructions coming soon
|
||||
## Updating double-conversion from Vendor to ICU4C
|
||||
|
||||
The relevant files from double-conversion are copied (svn cp) from Vendor to icu4c/source/i18n. In order to integrate changes from a new version of double-conversion, the changes in Vendor after updating from Github should be merged into their corresponding copies in ICU4C.
|
||||
|
||||
Instructions on how to do this should be written by the first person who performs such an update.
|
||||
|
||||
For reference, the original commit including all of the svn copies is here:
|
||||
|
||||
http://bugs.icu-project.org/trac/changeset/40929
|
||||
|
|
Loading…
Add table
Reference in a new issue