From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [commit] Last major piece of fork tracing - vfork/exec
Date: Fri, 22 Aug 2003 18:40:00 -0000 [thread overview]
Message-ID: <3F4663B6.7000700@redhat.com> (raw)
In-Reply-To: <200308221553.h7MFrP2p013327@duracef.shout.net>
> I hate to cause trouble here. We're all on edge with the release
> coming up (and this is also end-of-quarter for the red hat people).
> But I have to speak up.
(I never no when EOQ is so thanks for the heads up).
> The release is already being held up for the gdb.c++ -> gdb.cp
> renaming. The one-week comment period for that change ends this
> afternoon. Then I can commit this change to gdb HEAD. Then it
> needs a shakedown period in gdb HEAD. Then I can commit the
> change to gdb gdb_6_0-branch, and it will need a shakedown period
> there as well.
The shake down will be telling people to do a cvs update -d
src/gdb/testsuite/gdb.cp.
> Andrew, I'm frankly amazed that you decided this feature was
> release critical, but that's okay. My role is to get it into
> the branch expeditiously.
The release isn't been held up for the gdb.cp rename, it happened to
slip nicely into the schedule. If it's not done by Sunday, I can easily
do it myself. The bottom line is that if it screws up, and the
testsuite is a brick, no one will notice. GDB on GNU/Linux will still work.
On the other hand, if vfork/exec breaks, GNU/Linux breaks and everyone
notices.
Andrew
next prev parent reply other threads:[~2003-08-22 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 15:53 Michael Elizabeth Chastain
2003-08-22 18:40 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-25 1:19 Michael Elizabeth Chastain
2003-08-25 15:06 ` Andrew Cagney
2003-08-22 19:36 Michael Elizabeth Chastain
2003-08-22 22:07 ` Andrew Cagney
2003-08-17 20:19 Daniel Jacobowitz
2003-08-18 15:46 ` Andrew Cagney
2003-08-22 15:32 ` Andrew Cagney
2003-08-22 21:20 ` Daniel Jacobowitz
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=3F4663B6.7000700@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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