diff options
| author | abcd <abcd@gentoo.org> | 2009-12-13 12:43:03 -0500 |
|---|---|---|
| committer | abcd <abcd@gentoo.org> | 2009-12-13 12:44:29 -0500 |
| commit | 3468d2f920f220d2ca1acadad526a0a96dd652d2 (patch) | |
| tree | 201779d8c90d3ff13670c05415a44cccd25bfac0 /Documentation/CODE | |
| parent | 5f81d4b328b60d10daeb9ddb1914991e3f3dda38 (diff) | |
| download | kde-3468d2f920f220d2ca1acadad526a0a96dd652d2.tar.gz kde-3468d2f920f220d2ca1acadad526a0a96dd652d2.tar.bz2 kde-3468d2f920f220d2ca1acadad526a0a96dd652d2.zip | |
[Documentation] Remove unused script (it still had 4.2.1 hardcoded...); kde-testing -> kde in the couple places that haven't changed yet
Diffstat (limited to 'Documentation/CODE')
| -rw-r--r-- | Documentation/CODE | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/CODE b/Documentation/CODE index 09e962a0c82..dce53a181a4 100644 --- a/Documentation/CODE +++ b/Documentation/CODE @@ -1,7 +1,7 @@ WHAT RULES I SHOULD FOLLOW WHEN I WANT TO WORK ON SOMETHING FOR KDE TEAM? If you asked this question you are reading the right file. -KDE4 (kde-testing) policies: +KDE4 policies: - NEVER EVER COMMIT NEW REVBUMPS NOR MAJOR CHANGES TO TREE DIRECTLY - ALWAYS USE overlay first so that more pairs of eyes can spot issues. Especially anything in kde-base. |