Lines Matching +full:single +full:- +full:master

10 -----------
14   Agreement](https://developers.google.com/open-source/cla/individual),
19   things--for instance that you will tell us if you know that your code
27   Agreement](https://developers.google.com/open-source/cla/corporate).
32   changes to Google Inc. and use the 3-clause BSD license text included
34   owned by a single entity is important, particularly to avoid the problem of
40 -------------
44   [kyua-discuss mailing
45   list](https://groups.google.com/forum/#!forum/kyua-discuss)
50   [kyua-log mailing list](https://groups.google.com/forum/#!forum/kyua-log) to
55 ------------
57 * Always work on a non-master branch.
59 * Make sure the history of your branch is clean.  (Ab)use `git rebase -i master`
70 * It is OK and expected for you to `git push --force` on **non-master**
72   more than once for any given branch after you have "fixed-up" commits to
81 ------------
83 * All changes will be subject to code reviews pre-merge time.  In other words:
97   diff by typing `git diff <your-branch> master`.
101 ---------------
105   the whole commit.  Then a blank line comes, and then multiple plain-text
107   72-75 characters per line.  Vim has syntax highlighting for Git commit
110 * Use the imperative tense.  Say `Add foo-bar` or `Fix baz` instead of `Adding
115 ---------------------------
117 * All changes pushed to `master` should cross-reference one or more issues in
121 * Unless you have a good reason to do otherwise, name your branch `issue-N`
124 * If the fix to the issue can be done *in a single commit*, terminate the commit
127   be merged onto master using fast-forward (the default behavior of `git
133   belong in the merge commit onto `master`, which is done by `git merge --no-ff
134   --no-commit your-branch`, followed by an edit of `NEWS`, and terminated with a
135   `git commit -a` with the proper note on the bug being fixed.
139 -----------
141 These notes are generic and certainly *non-exhaustive*:
149   *single tab*.
152   grammar.](http://julipedia.meroh.net/2013/06/readability-mind-your-typos-and-grammar.html)
164 * Two spaces after end-of-sentence periods.