From 3468d2f920f220d2ca1acadad526a0a96dd652d2 Mon Sep 17 00:00:00 2001 From: abcd Date: Sun, 13 Dec 2009 12:43:03 -0500 Subject: [Documentation] Remove unused script (it still had 4.2.1 hardcoded...); kde-testing -> kde in the couple places that haven't changed yet --- Documentation/CODE | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Documentation/CODE') 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. -- cgit v1.2.3