public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB schedule.
Date: Mon, 06 Oct 2003 20:50:00 -0000	[thread overview]
Message-ID: <3F81D598.4070601@redhat.com> (raw)
In-Reply-To: <200310061954.h96JsfCP008508@duracef.shout.net>

> I would rather skip gdb 6.0.1 unless something happens in the field
> that mandates it.  Less work on the branch => more resources for HEAD.

Apparently location expressions don't work (I'm wondering why the test 
results didn't identify this, sigh).

The fix is small so its the sort of thing that can be cheaply pushed 
into 6.0.1.

However, yes, given the choice, I'd also also prefer to not do a 6.0.1.

Andrew


  reply	other threads:[~2003-10-06 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 19:59 Michael Elizabeth Chastain
2003-10-06 20:50 ` Andrew Cagney [this message]
2003-10-06 21:06   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-10-06 18:37 Andrew Cagney

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=3F81D598.4070601@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).