From 742d7721b22e8191dbc0e2e0a0b827d2708dc6c4 Mon Sep 17 00:00:00 2001 From: Sami Kerola Date: Wed, 7 Jan 2015 19:25:39 +0000 Subject: docs: add howto-pull-request.txt Reference: http://comments.gmane.org/gmane.linux.utilities.util-linux-ng/10431 Signed-off-by: Sami Kerola --- Documentation/howto-contribute.txt | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'Documentation/howto-contribute.txt') diff --git a/Documentation/howto-contribute.txt b/Documentation/howto-contribute.txt index 554d6b324..6d3e7892d 100644 --- a/Documentation/howto-contribute.txt +++ b/Documentation/howto-contribute.txt @@ -10,8 +10,9 @@ Patches distribution-neutral. No RPMs/DEBs/... are provided - get yours from your distributor. - * patches are delivered via email only. Downloading them from - internet servers is a pain. + * patches are delivered via email or git remote repository only. + Downloading them from internet servers is a pain. See + howto-pull-request.txt for remote repository instructions. * one patch per email, with the changelog in the body of the email. @@ -112,6 +113,9 @@ Patching process * Mark resubmission with [PATCH v2]. Hint: git format-patch origin/master..yourbranch --subject-prefix='PATCH v2' + * Use of remote repository for resubmission can be good idea. + See also howto-pull-request.txt + * All patch submissions, big or small, are either commented, reject, or merge. When maintainer rejects a patch (series) it is pointless to resubmit. -- cgit v1.2.3-55-g7522