summaryrefslogtreecommitdiffstats
path: root/tapset/DEVGUIDE
diff options
context:
space:
mode:
authorJosh Stone <jistone@redhat.com>2009-02-19 20:00:31 -0800
committerJosh Stone <jistone@redhat.com>2009-02-19 20:00:31 -0800
commit377f3fa917795a4f39fbf8f22b20b0385eee13c1 (patch)
tree866840561cc30472ee84284af2be50e4b0fef7e4 /tapset/DEVGUIDE
parent398edb63c89f853606f68b316bb6528e2f9d76da (diff)
downloadsystemtap-steved-377f3fa917795a4f39fbf8f22b20b0385eee13c1.tar.gz
systemtap-steved-377f3fa917795a4f39fbf8f22b20b0385eee13c1.tar.xz
systemtap-steved-377f3fa917795a4f39fbf8f22b20b0385eee13c1.zip
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.
Diffstat (limited to 'tapset/DEVGUIDE')
-rw-r--r--tapset/DEVGUIDE9
1 files changed, 1 insertions, 8 deletions
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
-------------------