From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: Release schedule
Date: Tue, 30 Apr 2002 09:24:00 -0000 [thread overview]
Message-ID: <200204301624.g3UGOCp24280@duracef.shout.net> (raw)
Which branches are CURRENT and NEXT coming from?
Is CURRENT going to be gdb 5.2.1 from gdb_5_2-branch,
with NEXT coming from the trunk?
I'm trying to get a feel for how active the 5.2 branch will be.
Michael C
next reply other threads:[~2002-04-30 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 9:24 Michael Elizabeth Chastain [this message]
2002-04-30 18:22 ` Andrew Cagney
2002-04-30 20:56 ` Daniel Jacobowitz
2002-05-03 9:37 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 8:04 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=200204301624.g3UGOCp24280@duracef.shout.net \
--to=mec@shout.net \
--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