Lines Matching full:changes

19 changes where the contributor already has a GitHub account.
31 that are security-related, problem reports, works in progress, changes that are controversial
32 and need discussion, or changes that require specialized review.
36 * The request is substantive in nature. We generally don't accept minor or cosmetic changes unless …
40 * It touches fewer than about 10 files and the changes are less than about 200 lines. Changes large…
43 * The scope of the pull request should not change during review. If the review suggests changes tha…
51 …deally, you'd also create a test case that shows an actual bug that's being fixed by these changes.
59 More complex changes may be submitted as pull requests, but they may be closed
77 their own consistent style that deviates from style(9). Style changes take time
79 their time. Trivial spelling changes take this valuable time, but rerturn little
80 benefit relative to other changes.
110 it to contact you. We can use `.mailmap` for name or email changes and mistakes,
113 Core (core@freebsd.org) may request authors of significant changes using an
128 command can help minimize churn by only formatting the areas nearby the changes. While
136 For Makefiles changes, see
142 For manual page changes, see
144 for details. Changes should pass `mandoc -Tlint` and igor (install the latter with `pkg install igo…
146 Proposed changes to manual pages should not bump the document date until merged.