Lines Matching +full:on +full:- +full:the +full:- +full:go

1 See README.hackers for notes on coding styles.
3 The NTP project's github repository is at https://github.com/ntp-project/ntp.
7 The stable branch is the current supported production code branch, the
8 ntp-stable code (even 2nd number).
10 The master branch is for new development, also known as ntp-dev (which
14 in seeing that work in the current production release then base your work
15 on the stable branch, and pull your work into a master copy to allow for
16 publishing your changes in the ntp-dev or master branch.
18 If there is no expectation that your work will be included in the
19 current stable release (the ntp-stable code) then it's better to do your
20 work on a copy of the master branch.
32 handled sooner if the repo that contains your pull requests also includes
35 The general workflow is as follows:
37 1) If you haven't, create a fork of ntp-project/ntp with your github account.
38    i) Log on to github.com with your github account.
39 …- If you don't have one, create one first. (read: https://help.github.com/articles/signing-up-for-…
40        - Make sure you also have a SSH key associated with your github account.
41          (read: https://help.github.com/articles/generating-ssh-keys/)
42    ii) Go to https://github.com/ntp-project/ntp
43    iii) On the top right corner, right below the header bar, there is
44         a button labeled "Fork".  Click on it.  This will fork the current
45 	ntp master to your own account. Once done, it will go to your account's
46 	version of the ntp repository. (Your fork of ntp source)
48         - git clone git@github.com:<your_username>/ntp
50 2) Look through the bugs listed in the bug tracker: http://bugs.ntp.org/
52 3) Once you've found a bug to work on:
55       (the <branchname> can be any valid short string that will tell you
56        what you're working on)
57       - git checkout -b <branchname>
59    ii) Start working on the bug.
60    iii) When you create changes in the source, it would help you to 
63 	 made a mistake, you can always go back.)
64 	 - git commit -a -m "description of change"
67          - git push origin <branchname>
68     v) (go to step iii).
70 4) Once you feel you've fixed the bug (and tested it), you need to 
71    create a pull request on your branch on github.  (Read up on
72    pull requests @ https://help.github.com/articles/using-pull-requests)
74     i) Create your pullrequest by following the instructions @
75        https://help.github.com/articles/creating-a-pull-request/
78    passes review, it will be merged by the reviewer/allowed committer.
82 If these patches are for a bugzilla issue, mark the issue as Resolved/READY
83 with a comment of "Please pick up the patches from XXX" where XXX is
86  hostname:~user/path	if it's a machine the reviewers have access to, or
87  github-pull-request-URI
89 ---