From: Thomas Dineen <tdineen@ix.netcom.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Fri, 22 Feb 2008 17:37:00 -0000 [thread overview]
Message-ID: <47BF0478.1050209@ix.netcom.com> (raw)
In-Reply-To: <18366.14530.875406.113087@kahikatea.snap.net.nz>
Gentle People:
Yes but with the conditions listed below:
"robustly constructed and justified"
any contributor can easily be blown off for
any political reason!
From my observations the attitudes expressed
in this thread are NOT positive for the Open Source
Movement. I would suggest that your movement would
benefit from more openness and democracy.
Thomas Dineen
Nick Roberts wrote:
> > Please don't be disappointed by mere politics. If your technical
> > contributions continue, and are robustly constructed and justified,
> > any reasonable maintainer will have no choice but to go along. A
> > powerful contributor can outproduce a maintainer, and in the end
> > that's what matters.
>
>Thanks but I'm probably not really a powerful contributor. I just wanted to be
>able to commit patches in a timely fashion and somehow thought if I put in the
>hard yards that one day I would be able to do so.
>
>
>
next prev parent reply other threads:[~2008-02-22 17:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 19:37 Daniel Jacobowitz
2008-02-19 20:29 ` Nick Roberts
2008-02-19 20:46 ` Daniel Jacobowitz
2008-02-19 20:47 ` Nick Roberts
2008-02-21 1:43 ` Daniel Jacobowitz
2008-02-20 3:12 ` Bob Rossi
2008-02-20 8:59 ` Richard Stallman
2008-02-21 21:37 ` Bob Rossi
2008-02-20 19:05 ` Richard Stallman
2008-02-20 20:00 ` Nick Roberts
2008-02-20 20:57 ` Eli Zaretskii
2008-02-20 21:20 ` Nick Roberts
2008-02-20 21:50 ` Joel Brobecker
2008-02-20 23:25 ` Frank Ch. Eigler
2008-02-22 3:34 ` Nick Roberts
2008-02-22 17:37 ` Thomas Dineen [this message]
2008-02-22 22:09 ` Eli Zaretskii
2008-02-22 22:14 ` Christopher Faylor
2008-02-22 22:23 ` Bob Rossi
2008-02-23 0:01 ` Dave Korn
2008-02-23 0:58 ` Alpár Jüttner
2008-02-23 8:16 ` Jim Blandy
2008-02-23 11:13 ` Nick Roberts
2008-02-23 11:15 ` Eli Zaretskii
2008-02-23 12:34 ` Eli Zaretskii
2008-02-22 23:36 ` Jim Blandy
2008-02-21 19:25 ` Stan Shebs
2008-02-22 4:08 ` Nick Roberts
2008-02-22 2:52 ` Bob Rossi
2008-02-22 8:43 ` Vladimir Prus
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=47BF0478.1050209@ix.netcom.com \
--to=tdineen@ix.netcom.com \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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