From 6a6ccc1de6c19ff3c77c10491d5f8b65759cff4a Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Tue, 10 Aug 1999 09:34:35 +0000 Subject: [PATCH] Added an HACKING file, Daniel. --- ChangeLog | 4 ++++ HACKING | 26 ++++++++++++++++++++++++++ 2 files changed, 30 insertions(+) create mode 100644 HACKING diff --git a/ChangeLog b/ChangeLog index 5d1e2cb0..6e500e45 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +Tue Aug 10 11:33:41 CEST 1999 Daniel Veillard + + * Added an HACKING file + Tue Jul 27 21:43:00 CEST 1999 Daniel Veillard * xpath.[ch] : improvements and debug of the XPath implementation diff --git a/HACKING b/HACKING new file mode 100644 index 00000000..6b702fa5 --- /dev/null +++ b/HACKING @@ -0,0 +1,26 @@ + + Rules for commits on the gnome-xml 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. + +Otherwise, send me (Daniel.Veillard@w3.org) a mail and if it's a bug +issue, register it at bugs.gnome.org. I check both my mail and the +bug database everyday. if you don't get an answer within 3 days +(which is highly unprobable) then commit your changes. This simply +mean that I'm on holliday or on the road. + +The reasons I'm asking for an ask before commit policy is that I'm +using a separate CVS base for unstable developments and if you commit +a patch I didn't get, I may loose your change by mistake (it happened +already once) and seriously complicatye my job of merging both bases. +(The second base is at http://dev.w3.org/ under the XML module). + + thanks in advance for following the rule, + +Daniel + +P.S.: Raph Levien get an exception for the send before commit rule :-) +