Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 5.3.1 vs 5.4/6.0
Date: Thu, 02 Jan 2003 15:41:00 -0000	[thread overview]
Message-ID: <20030102154116.GC693@gnat.com> (raw)
In-Reply-To: <3E145BA0.4050403@redhat.com>

> Still, the question is: should the next release be 5.3.1, or 5.4/6.0?
> 
> 5.3.1 would be something like end Jan / start Feb.
> 5.4/6.0 branch would be ~March.

I think we have enough valuable fixes in the 5.3 branch to make a 5.3.1
release worth-while.

> (As for 5.4 vs 6.0, I don't think the multi-arch goal will have been
> achieved.)

Apart from HP/UX (my bad, sorry sorry sorry, I've been sooo busy, I
didn't even take a christmas break), which platforms still need to be
converted before we can go to 6.0?

-- 
Joel


  reply	other threads:[~2003-01-02 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 15:33 Andrew Cagney
2003-01-02 15:41 ` Joel Brobecker [this message]
2003-01-02 17:16   ` Andrew Cagney
2003-01-02 17:29     ` Joel Brobecker
2003-01-02 18:55       ` Andrew Cagney
2003-01-02 17:34 ` Daniel Jacobowitz
2003-01-02 19:01   ` Andrew Cagney
2003-01-02 17:19 Michael Elizabeth Chastain
2003-01-02 17:22 Michael Elizabeth Chastain

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=20030102154116.GC693@gnat.com \
    --to=brobecker@gnat.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.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