1Contributing to the tz code and data
2
3The time zone database is by no means authoritative: governments
4change timekeeping rules erratically and sometimes with little
5warning, the data entries do not cover all of civil time before
61970, and undoubtedly errors remain in the code and data. Feel
7free to fill gaps or fix mistakes, and please email improvements
| 1Contributing to the tz code and data
2
3The time zone database is by no means authoritative: governments
4change timekeeping rules erratically and sometimes with little
5warning, the data entries do not cover all of civil time before
61970, and undoubtedly errors remain in the code and data. Feel
7free to fill gaps or fix mistakes, and please email improvements
|
8to tz@iana.org for use in the future. In your email, please give
9reliable sources that reviewers can check.
| 8to tz@iana.org for use in the future.
|
10
| 9
|
11-----
12
13Developers can contribute technical changes to the source code and
14data as follows.
15
| |
16To email small changes, please run a POSIX shell command like
17'diff -u old/europe new/europe >myfix.patch', and attach
18myfix.patch to the email.
19
| 10To email small changes, please run a POSIX shell command like
11'diff -u old/europe new/europe >myfix.patch', and attach
12myfix.patch to the email.
13
|
20For more-elaborate changes, please read the theory.html file and browse
21the mailing list archives <https://mm.icann.org/pipermail/tz/> for
22examples of patches that tend to work well. Additions to
| 14For more-elaborate changes, please read the Theory file and browse
15the mailing list archives for
16examples of patches that tend to work well. Ideally, additions to
|
23data should contain commentary citing reliable sources as
| 17data should contain commentary citing reliable sources as
|
24justification. Citations should use https: URLs if available.
| 18justification.
|
25
26Please submit changes against either the latest release in
| 19
20Please submit changes against either the latest release in
|
27<https://www.iana.org/time-zones> or the master branch of the development
28repository. If you use Git the following workflow may be helpful:
| 21<ftp://ftp.iana.org/tz/> or the master branch of the experimental
22Git repository. If you use Git the following workflow may be helpful:
|
29
| 23
|
30 * Copy the development repository.
| 24 * Copy the experimental repository.
|
31
32 git clone https://github.com/eggert/tz.git
33 cd tz
34
35 * Get current with the master branch.
36
37 git checkout master
38 git pull
--- 41 unchanged lines hidden --- | 25
26 git clone https://github.com/eggert/tz.git
27 cd tz
28
29 * Get current with the master branch.
30
31 git checkout master
32 git pull
--- 41 unchanged lines hidden --- |