Lines Matching refs:patches

4 Sending patches
13 repository, and then submit these patches for review through a merge request.
15 Wayland formerly accepted patches via `git-send-email`, sent to
18 Some old patches continue to be sent this way, and we may accept small new
19 patches sent to the list, but please send all new patches through GitLab merge
74 Your patches should also include a Signed-off-by line with your name and
82 We won't reject patches that lack S-o-b, but it is strongly recommended.
84 When you re-send patches, revised or not, it would be very good to document the
89 deserve, and the patches may cause redundant review effort.
92 Tracking patches and following up
95 Once submitted to GitLab, your patches will be reviewed by the Wayland
101 If you do get asked to revise the patches, please bear in mind the notes above.
102 You should use `git rebase -i` to make revisions, so that your patches follow
107 A common request is to split single large patch into multiple patches. This can
125 list of available patches.
212 All patches, even trivial ones, require at least one positive review
282   spelling fixes and whitespace adjustment) patches that have been merged
287   review other peoples patches but just make sure that patch submission isn't
290 - Will be regularly contributing further patches. This includes regular