From fde3fa2f32a7ace25e2eca7e6b9b07878ca3ddc0 Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Mon, 18 Jun 2001 22:21:10 +0000 Subject: [PATCH] - HACKING: fixed, added William Daniel --- ChangeLog | 4 ++++ HACKING | 9 +++++---- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index 127806a..5d3dabe 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +Tue Jun 19 00:20:32 CEST 2001 Daniel Veillard + + * HACKING: fixed, added William + Mon Jun 18 18:36:36 CEST 2001 Daniel Veillard * libxslt/xsltutils.c: forgot to flush in xsltSaveTo() in html and diff --git a/HACKING b/HACKING index 64a3aca..605cdaa 100644 --- a/HACKING +++ b/HACKING @@ -1,13 +1,14 @@ Rules for commits on the libxslt module ======================================= -If what you are patching is a non-compilation issue either at compile +If what you are fixing is a 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. +Otherwise, oly Bjorn Reese (breese@users.sourceforge.net), +"William M. Brack" and me (veillard@redhat.com) +should commit there. Send a mail and if it's a bug issue, +patchingregister 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 -- 2.7.4