diff options
Diffstat (limited to 'README.CVS')
| -rw-r--r-- | README.CVS | 23 |
1 files changed, 19 insertions, 4 deletions
diff --git a/README.CVS b/README.CVS index abfbc7750..b0c531b2e 100644 --- a/README.CVS +++ b/README.CVS @@ -1,4 +1,4 @@ -Mauro Carvalho Chehab 2005 Dec 02 +Mauro Carvalho Chehab 2005 Dec 08 CVS is a developer database, It means that it might be broken from time to time. There are more "stable" snapshots at @@ -73,7 +73,7 @@ export CHANGE_LOG_NAME CHANGE_LOG_EMAIL_ADDRESS CHANGE_LOG_LOGIN Obs.: Timestamp should be in GMT. - 9) Commit messages are very rellevant, since they will be used + 10) Commit messages are very rellevant, since they will be used when generating the patches for mainstream. The format of commit message shall be: Subject: patch subject @@ -89,14 +89,14 @@ Signed-off-by: Cvs Maintainer <cvsmaintainer@cvsmaintainersite.com> You may add other signers, if the patch were tested by somebody else and he also wants to sign. - 10) if the patch also affects other parts of kernel (like alsa + 11) if the patch also affects other parts of kernel (like alsa or i2c), it is required that, at upstream submiting, the patch also go to the maintainers of that piece. To do this, CVS maintainer shall add one or more cc: fields at commit cvs message: CC: someotherkerneldeveloper@someplace - 11) Sometimes, mainstream changes do affect CVS tree, and + 12) Sometimes, mainstream changes do affect CVS tree, and requires to apply some kernel patches at the tree. This kind of commit should follow the rules above and should also have a line like: @@ -104,5 +104,20 @@ kernel-sync Patches with such lines will not be submited upstream. + 13) sometimes, it is necessary to introduce some testing code +or remove parts that are not yet finished. Also, compatibility tests +maybe required. + To allow compatibility tests, "compat.h" should be included +first. It does include also linux/version.h. + To include testing code, #if 0 or #if 1 may be used. +If this code is meant to go also to kernel, this struct shuld be used: +#if 0 /* keep */ + or +#if 1 /* keep */ + + 14) Nested #ifs are allowed, but #elsif macro shouldn't be used, +since the macro preprocessing script used to prepare kernel upstream +patches (v4l/scripts/gentree.pl) is not able to handle it. + Mauro Mauro Carvalho Chehab <mchehab .at. linuxtv .dot. org> |