Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Rossi <bob_rossi@cox.net>
Cc: gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Sat, 23 Feb 2008 12:34:00 -0000	[thread overview]
Message-ID: <ulk5bj553.fsf@gnu.org> (raw)
In-Reply-To: <20080222222124.GH26716@brasko.net> (message from Bob Rossi on 	Fri, 22 Feb 2008 17:21:24 -0500)

> Date: Fri, 22 Feb 2008 17:21:24 -0500
> From: Bob Rossi <bob_rossi@cox.net>
> 
> > It's interesting how often people try to tack on bigger concerns to the
> > simple concept of Free Software.  Free Software isn't supposed to be
> > solving global warming and it isn't supposed to be a demonstration of a
> > New World Order with feel-good cum ba yah.  It's just a guarantee that
> > you get the source code for the software that you're using.
> > 
> > Managing any project where people are involved means that sometimes the
> > people in charge have to have frank, private conversations.  The
> > alternative, as Stan Shebs, notes is to essentially do performance
> > reviews in the open.
> > 
> > Some projects *do* work that way but they are hardly bastions of
> > civilized discourse.
> 
> This rhetoric annoys me. I was bringing up a sincere concern that I
> have. I suggested a more open model because I've been wondering for 
> well over 5 years why it (used to?) takes 6 months to get a code review.

The long review time has nothing to do with the issue at hand, or with
the above rhetoric.


  parent reply	other threads:[~2008-02-23 11:15 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
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 [this message]
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=ulk5bj553.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bob_rossi@cox.net \
    --cc=gdb@sourceware.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