README.patches revision 132451 
1See README.hackers for notes on coding styles.
2
3If you are going to patch both ntp-stable and ntp-dev
4please do it this way:
5
6 > cd ntp-stable
7 > (make and test your changes to ntp-stable first)
8 > (commit your changes to ntp-stable)
9 > cd ../ntp-dev
10 > bk pull ../ntp-stable	(get your changes from ntp-stable)
11 > (resolve any problems and test your changes)
12 > (commit your changes to ntp-dev)
13
14With the current release of bitkeeper it is *much* easier to move changes
15from ntp-stable to ntp-dev than it is to move changes from ntp-dev to
16ntp-stable.
17
18If you make your changes in the above order and then submit them,
19it will be trivial to apply your patches.
20
21Otherwise, it will be much more difficult to apply your patches.
22
23---
24
25Please read (and follow) the previous section if you want to submit
26patches for both ntp-stable and ntp-dev.
27
28To submit patches please use the 'bk send' command:
29
30 > cd REPO
31 > bk citool	(or bk ci ... ;  bk commit ... )
32 > bk pull	# make sure your repo is up-to-date
33 > bk send -d -ubk://www.ntp.org/home/bk/REPO - > file-containing-the-patch
34 > bk receive -vv -a < file-containing-the-patch
35		# Sanity check.
36
37 # Open a bugzilla item at <http://bugzilla.ntp.org>
38
39 # After the bug is opened, visit the bug and attach file-containing-the-patch
40