Intolerable CVS behaviour



  Okay, I was about to commit in the gnome-xml module.
Got message that the code wan't up to date, surprizing, I upgraded,
this removed a large amount of the file from my CVS tree, moving stuff
like xpath.c to Attic (though it's a vital component for the libxslt)

  I rush to see teh Changelog and see:

-----------------------------------------
Thu Feb 23 02:03:56 CET 2001 Tomasz Kłoczko <kloczek pld org pl>

        * *.c *.h libxml files: moved to libxml directory - this allow
          simplify automake/autoconf. Now isn't neccessary hack on
          am/ac level for make and remove libxml symlink (modified for this
          also configure.in and main Makefile.am). Now automake abilities
          are used in best way (like in many other projects with libraries).
        * include/win32config.h: moved to libxml directory (now include
          directory isn't neccessary).
        * Makefile.am, examples/Makefile.am, libxml/Makefile.am:
          added empty DEFS and in INCLUDES rest only -I$(top_builddir) -
          this allow minimize parameters count passed to libtool script
          (now compilation is also slyghtly more quiet).
        * configure.in: simplifies libzdetestion - prepare separated
          variables for keep libz name and path to libz header files isn't
          realy neccessary (if someone have libz installed in non standard
          prefix path to header files ald library can be passed as:
          $ CFALGS="-I</libz.h/path>" LDFLAGS="-L</libz/path>" ./configure
        * autogen.sh: check now for libxml/entities.h.

        After above building libxml pass correctly and also pass
        "make install DESTDIR=</install/prefix>" from tar ball generated by
        "make dist". Seems ac/am reorganization is finished. This changes
        not touches any other things on *.{c,h} files level.

-----------------------------------------

the HACKING *explicitely* says:

------------------------------------------
     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 complicates 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,
------------------------------------------

  So this person:
   - didn;t bothered to read the HACKING
   - commited huge change, loosing the history for all my modules
   - didn't even sent a mail before to ask the maintainer, didn't
     contacted the mailing list either

  I'M FUCKING PISSED !!!! I just can't express how much I am frustrated
Who gave this guy commit access? for what work ? Who recommended him ?

  I ask he be first removed CVS commit capability,
and I ask for help to recover the previous setup of
gnome-xml head,

  thanks in advance,

Daniel

-- 
Daniel Veillard      | Red Hat Network http://redhat.com/products/network/
veillard redhat com  | libxml Gnome XML toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]