public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: 6.0 release schedule; Was: 6.0 issues
Date: Fri, 22 Aug 2003 15:02:00 -0000	[thread overview]
Message-ID: <3F46306D.3040300@redhat.com> (raw)
In-Reply-To: <3F41053F.5080304@redhat.com>


> I should add, I'm thinking of rolling out a draft this weekend (2003-08-23), and the final a week later (2003-08-30ish).

In light of some recent follow-fork changes, I'm going to toss in an 
extra week:

2003-08-24-gmt: draft
2003-08-32-gmt: final

Andrew


  reply	other threads:[~2003-08-22 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18 15:53 Andrew Cagney
2003-08-18 16:18 ` David Carlton
2003-08-18 16:46 ` Andrew Cagney
2003-08-18 16:56 ` Andrew Cagney
2003-08-22 15:02   ` Andrew Cagney [this message]
2003-08-22 15:33     ` 6.0 release schedule; Was: " H. J. Lu
2003-08-22 15:35     ` 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=3F46306D.3040300@redhat.com \
    --to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).