summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@infradead.org>2007-09-06 12:13:11 +0100
committerMauro Carvalho Chehab <mchehab@infradead.org>2007-09-06 12:13:11 +0100
commit8d6f1ae6d289254a97015ac9629d831f06c9966a (patch)
tree43ac38be0a1ef8916f9c47038c92a93725ff072a
parent858685883b478121d9d72779c6a691f62d8da3ac (diff)
downloadmediapointer-dvb-s2-8d6f1ae6d289254a97015ac9629d831f06c9966a.tar.gz
mediapointer-dvb-s2-8d6f1ae6d289254a97015ac9629d831f06c9966a.tar.bz2
Add the "commit earlier, commit often concept"
From: Mauro Carvalho Chehab <mchehab@infradead.org> Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
-rw-r--r--README.patches8
1 files changed, 8 insertions, 0 deletions
diff --git a/README.patches b/README.patches
index 90ae313d8..e2ebb3670 100644
--- a/README.patches
+++ b/README.patches
@@ -319,6 +319,14 @@ k) By submitting a patch to the subsystem maintainer, either via email
later. If no specific clause are added, the added code will be
assumed as GPLv2 only.
+l) "Commit earlier and commit often". This is a common used rule at
+ Kernel. This means that a sooner submission of a patch will mean that
+ a review can happen sooner, and help the develop to address the
+ comments. This helps to reduce the life-cicle for having a changeset
+ committed at kernel at the proper time. It also means that the one
+ changeset should idally address just one issue. So, mixing different
+ things at the same patch should be avoided.
+
5. Knowing about newer patches committed at master hg repository
=============================================================