Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: nickrob@snap.net.nz, vladimir@codesourcery.com,
	        gdb-patches@sources.redhat.com
Subject: Re: MI: frozen variable objects
Date: Sat, 18 Nov 2006 11:00:00 -0000	[thread overview]
Message-ID: <uwt5taukm.fsf@gnu.org> (raw)
In-Reply-To: <20061117210501.GA13104@nevyn.them.org> (message from Daniel 	Jacobowitz on Fri, 17 Nov 2006 16:05:01 -0500)

> Date: Fri, 17 Nov 2006 16:05:01 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <vladimir@codesourcery.com>, 	gdb-patches@sources.redhat.com
> > 
> > If the changes go in after the release I generally have six months to spot a
> > bug, if they go in now I'll have roughly two weeks.
> 
> I don't get the fuss.  It's not an immensely destabilizing change or a
> huge new subsystem.  Why should it be treated separately from any other
> patch posted in the last few months, in the later half of a release
> gap?

Two weeks does seem a tad too short, much shorter than ``the last few
months''.  While you are right that the change is not immensely
destabilizing, I'm sure you can understand Nick's concern for the
quality of the released GDB, even if only in relatively minor
features.

> Let me be perfectly clear about this.  I can spend a certain amount of
> my work time reviewing community patches, because my employer is very
> understanding about the FSF development process.  I'm lucky in that
> respect and hopefully so is GDB.

Yes, we are extremely lucky that we have you, Daniel, and that you can
do such a wonderful job for so many hours a day.  I'm sure Nick didn't
mean any disrespect.

> And more maintainers.

Absolutely.  Any suggestions welcome.

> All: Should Nick be an MI maintainer now?

I vote in favor.


  parent reply	other threads:[~2006-11-18 11:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 21:53 Nick Roberts
2006-11-16 22:00 ` Daniel Jacobowitz
2006-11-16 23:07   ` Nick Roberts
2006-11-17 15:19     ` Daniel Jacobowitz
2006-11-17 20:52       ` Nick Roberts
2006-11-17 21:05         ` Daniel Jacobowitz
2006-11-17 23:12           ` Nick Roberts
2006-11-18 11:00           ` Eli Zaretskii [this message]
2006-11-17  6:25 ` Vladimir Prus
2006-11-17 18:14 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-11-18  6:59 Nick Roberts
2006-11-16 12:48 Vladimir Prus
2006-11-16 13:58 ` Greg Watson
2006-11-16 15:25   ` Frederic RISS
2006-11-16 15:55     ` Daniel Jacobowitz
2006-11-16 16:26       ` Frederic RISS
2006-11-16 16:34         ` Daniel Jacobowitz
2006-11-17 15:21       ` Greg Watson
2006-11-16 18:55     ` Vladimir Prus
2006-11-16 21:36       ` Frédéric Riss
2006-11-17  6:17         ` Vladimir Prus
2006-11-17  8:54           ` Frederic RISS
2006-11-16 18:47   ` Vladimir Prus
2006-11-17 15:09     ` Greg Watson
2006-11-17 15:15       ` Daniel Jacobowitz
2006-11-17 15:26         ` Greg Watson
2006-11-17 15:33           ` Daniel Jacobowitz
2006-11-17 15:41             ` Greg Watson
2006-11-17 15:45               ` Daniel Jacobowitz
2006-11-17 18:16               ` Daniel Jacobowitz
2006-11-17 15:35         ` Greg Watson
2006-11-17 15:27       ` 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=uwt5taukm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    --cc=vladimir@codesourcery.com \
    /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