From 76b8fca1a6edea7ff871b82ba9304029d5599735 Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Tue, 13 Mar 2001 09:31:39 +0000 Subject: [PATCH] - README.cvs-commits: added, pointing to HACKING - HACKING: added defines commit rules. Daniel --- ChangeLog | 5 +++++ HACKING | 19 +++++++++++++++++++ README.cvs-commits | 5 +++++ 3 files changed, 29 insertions(+) create mode 100644 HACKING create mode 100644 README.cvs-commits diff --git a/ChangeLog b/ChangeLog index f1059d2..2b3bfd4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Tue Mar 13 10:29:45 CET 2001 Daniel Veillard + + * README.cvs-commits: added, pointing to HACKING + * HACKING: added defines commit rules. + Mon Mar 12 14:43:20 CET 2001 Daniel Veillard * libxslt/extra.c libxslt/variables.c: fixing compilation diff --git a/HACKING b/HACKING new file mode 100644 index 0000000..64a3aca --- /dev/null +++ b/HACKING @@ -0,0 +1,19 @@ + Rules for commits on the libxslt module + ======================================= + +If what you are patching is a non-compilation issue either at compile +time or linking time on one of the main Linux platforms, then feel free +to patch first and send mail afterward, as long as it's a 'small fix'. + +Otherwise, oly Bjorn Reese (breese@users.sourceforge.net) and me +(veillard@redhat.com) should commit there. Send a mail and if it's a +bug issue, register it at bugzilla.gnome.org in the libxslt module. +I check both my mail and the bug database on a very regular basis. +if you don't get an answer within a week (which is highly unprobable) +then commit your changes. This simply mean that I'm on holliday or +on the road. + + thanks in advance for following the rule, + +Daniel + diff --git a/README.cvs-commits b/README.cvs-commits new file mode 100644 index 0000000..a4bd841 --- /dev/null +++ b/README.cvs-commits @@ -0,0 +1,5 @@ + Please read the HACKING file for instructions + +Daniel + +$Id$ -- 2.7.4