summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorDaniel Veillard <veillard@src.gnome.org>2001-06-18 22:21:10 +0000
committerDaniel Veillard <veillard@src.gnome.org>2001-06-18 22:21:10 +0000
commitfde3fa2f32a7ace25e2eca7e6b9b07878ca3ddc0 (patch)
tree981c5b6bd0a941daa2ef0c959b0556c0946e32a3 /HACKING
parentb58357db78ea13cbd9a2817f775556b6eaa4aab0 (diff)
downloadlibxslt-fde3fa2f32a7ace25e2eca7e6b9b07878ca3ddc0.tar.gz
libxslt-fde3fa2f32a7ace25e2eca7e6b9b07878ca3ddc0.tar.bz2
libxslt-fde3fa2f32a7ace25e2eca7e6b9b07878ca3ddc0.zip
- HACKING: fixed, added William
Daniel
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING9
1 files changed, 5 insertions, 4 deletions
diff --git a/HACKING b/HACKING
index 64a3aca5..605cdaaa 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" <wbrack@mmm.com.hk> 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