linux-kernel - [RFC 4/4] Documentation: Provide suggestions on when to repost patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1418623790-28429-5-git-send-email-cernekee@gmail.com>
Date:	Sun, 14 Dec 2014 22:09:50 -0800
From:	Kevin Cernekee <cernekee@...il.com>
To:	tglx@...utronix.de, bp@...en8.de, gnomes@...rguk.ukuu.org.uk
Cc:	computersforpeace@...il.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, corbet@....net,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC 4/4] Documentation: Provide suggestions on when to repost patches

Give submitters a rough idea of how long to wait before reposting, to
help avoid situations where a series is reposted before the original
submission is fully reviewed.

Suggested-by: Thomas Gleixner <tglx@...utronix.de>
Signed-off-by: Kevin Cernekee <cernekee@...il.com>
---
 Documentation/development-process/6.Followthrough | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Documentation/development-process/6.Followthrough b/Documentation/development-process/6.Followthrough
index 41d324a..6cefb6c 100644
--- a/Documentation/development-process/6.Followthrough
+++ b/Documentation/development-process/6.Followthrough
@@ -74,7 +74,10 @@ around.
 One fatal mistake is to ignore review comments in the hope that they will
 go away.  They will not go away.  If you repost code without having
 responded to the comments you got the time before, you're likely to find
-that your patches go nowhere.
+that your patches go nowhere.  On the flipside, reposting an updated patch
+before the original has been fully reviewed can be a source of frustration
+too, so consider giving the reviewers ~3-7 calendar days (depending on
+patch complexity) before posting V2.
 
 Speaking of reposting code: please bear in mind that reviewers are not
 going to remember all the details of the code you posted the last time
-- 
2.1.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/