qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Just to add one single point
Date: Sun, 08 Apr 2007 12:00:43 +0200	[thread overview]
Message-ID: <1176026443.1516.176.camel@rapid> (raw)

The main problem here is that the less one can do when collaborating to
a project is to respect others work.
Then nobody should ever commit anything that touch the code he's not in
charge without previously formally do a proposal, wait for reactions and
discuss, taking care of others remarks, especially when this code might
break some features that are used and mandatory. If no reaction, yes the
thing can be commited with no modification. If there are reactions, they
have to be taken in care or at least discussed (the contradictors may be
wrong, for sure).

There were no proposal sent on this list. I did not received even a
single mail telling me there'll be changes in the code I maintain. Don't
say "it was discussed a lot and approved" when you did not even try to
contact one of the main developpers.
Apart the fact that the commited code implements broken concepts, if one
is not able to respect other people and their work, he just have to
start its own project and work on its own, not to pretend collaborating.

Mr Paul Brook did break the PREP and heathrow machines while doing
changes in the PCI code. There were some posts on this list reporting
this and he never even tried to fix what he broke. And now he's
complaining "I cannot test as it does not work". Looks like a bad joke,
no ?
Today, he's breaking more features without even taking care of the
implications of he's doing. Am I supposed to think this attitude is a
normal and respectuous one ? I'm sorry that I can't. This way of doing
is to be fixed or the project is dead or will become Mr Paul Brook
exclusive toy. If this is what he wants, he has to tell it, do not allow
anybody else to make any change in its "personal code" and let me remove
all the contributions I've made for years.

Regards.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

             reply	other threads:[~2007-04-08 10:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-08 10:00 J. Mayer [this message]
2007-04-08 14:11 ` [Qemu-devel] Just to add one single point Thiemo Seufer
2007-04-08 16:03   ` J. Mayer
2007-04-08 23:19 ` Paul Brook
2007-04-09  1:22   ` Mike Frysinger
2007-04-09 10:06   ` J. Mayer
2007-04-09 21:26   ` Rob Landley
2007-04-09 22:32     ` J. Mayer
2007-04-11 21:49       ` Rob Landley
2007-04-12  7:56         ` Re:Qemu-PPC problems (was [Qemu-devel] Just to add one single point) J. Mayer
2007-04-12 15:49           ` Qemu-PPC " Jason Wessel
2007-04-12 16:34             ` Jason Wessel
2007-04-12 20:20             ` J. Mayer
2007-04-12 21:23               ` Jason Wessel
2007-04-14 21:28             ` Rob Landley
2007-04-18 21:34             ` Rob Landley
2007-04-14 19:50           ` Rob Landley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1176026443.1516.176.camel@rapid \
    --to=l_indien@magic.fr \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).