blob: 8f791bc0ae50cb5997d0c21f2d16d3da6ae3c460 [file] [log] [blame]
Daniel Veillard6a6ccc11999-08-10 09:34:35 +00001
2 Rules for commits on the gnome-xml module
3 =========================================
4
5If what you are patching is a non-compilation issue either at compile
6time or linking time on one of the main Linux platforms, then feel free
7to patch first and send mail afterward.
8
9Otherwise, send me (Daniel.Veillard@w3.org) a mail and if it's a bug
10issue, register it at bugs.gnome.org. I check both my mail and the
11bug database everyday. if you don't get an answer within 3 days
12(which is highly unprobable) then commit your changes. This simply
13mean that I'm on holliday or on the road.
14
15The reasons I'm asking for an ask before commit policy is that I'm
16using a separate CVS base for unstable developments and if you commit
17a patch I didn't get, I may loose your change by mistake (it happened
Daniel Veillardc08a2c61999-09-08 21:35:25 +000018already once) and seriously complicates my job of merging both bases.
Daniel Veillard6a6ccc11999-08-10 09:34:35 +000019(The second base is at http://dev.w3.org/ under the XML module).
20
21 thanks in advance for following the rule,
22
23Daniel
24
25P.S.: Raph Levien get an exception for the send before commit rule :-)
26