/contrib/ntp/README.patches

 1See README.hackers for notes on coding styles.
 2
 3The master copy of this information can be found at:
 4
 5 http://support.ntp.org/Dev/MaintainerIssues#How_to_work_on_a_bug_using_BitKe
 6
 7If you are going to patch both ntp-stable and ntp-dev
 8please do it this way:
 9
10 > cd ntp-stable
11 > (make and test your changes to ntp-stable first)
12 > (commit your changes to ntp-stable)
13 > cd ../ntp-dev
14 > bk pull ../ntp-stable	(get your changes from ntp-stable)
15 > (resolve any problems and test your changes)
16 > (commit your changes to ntp-dev)
17
18With the current release of bitkeeper it is *much* easier to move changes
19from ntp-stable to ntp-dev than it is to move changes from ntp-dev to
20ntp-stable.
21
22If you make your changes in the above order and then submit them,
23it will be trivial to apply your patches.
24
25Otherwise, it will be much more difficult to apply your patches.
26
27You are pretty much done now if your repos are on pogo.udel.edu.
28
29If these patches are for a bugzilla issue, mark the issue as Resolved/READY
30with a comment of "Please pick up the patches in pogo:/wherever"
31
32---
33
34Please read (and follow) the previous section if you want to submit
35patches for both ntp-stable and ntp-dev.
36
37If you cannot easily get your patches to pogo, you may submit patches
38via the 'bk send' command:
39
40 > cd REPO
41 > bk citool	(or bk ci ... ;  bk commit ... )
42 > bk pull	# make sure your repo is up-to-date
43 > bk send -d -ubk://www.ntp.org/home/bk/REPO - > file-containing-the-patch
44 > bk receive -vv -a < file-containing-the-patch
45		# Sanity check.
46
47 # Open a bugzilla item at <http://bugzilla.ntp.org>
48
49 # After the bug is opened, visit the bug and attach file-containing-the-patch