From 377f3fa917795a4f39fbf8f22b20b0385eee13c1 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Thu, 19 Feb 2009 20:00:31 -0800 Subject: Update guidelines for the ChangeLog-less world Getting rid of ChangeLogs doesn't mean that we get a free ticket -- we now need to be more diligent about providing meaningful commit messages. I've updated the HACKING file with a first draft of new guidelines, but we may still revise what we feel is appropriate detail in the logs. I removed the ChangeLog section from the tapset/DEVGIDE entirely, and also fixed the path where examples are stored. --- tapset/DEVGUIDE | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) (limited to 'tapset/DEVGUIDE') diff --git a/tapset/DEVGUIDE b/tapset/DEVGUIDE index 62e1ecdd..e6bc3fb8 100644 --- a/tapset/DEVGUIDE +++ b/tapset/DEVGUIDE @@ -231,14 +231,7 @@ most important, it validates that the tapset can actually be used for something useful. If you can't write a script that uses the tapset in a meaningful way, perhaps you should rethink what the tapset provides. -Example scripts are stored in src/examples in GIT. - -Change Logs ------------ -Update the appropriate ChangeLog files with a brief description of your -additions and changes. Note that the change description you enter during -a "cvs commit" does not get added to the ChangeLog files. You must edit -the ChangeLog files directly and commit them as well. +Example scripts are stored in testsuite/systemtap.examples/ in GIT. Embedded C & Safety ------------------- -- cgit