From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Last major piece of fork tracing - vfork/exec
Date: Fri, 22 Aug 2003 15:32:00 -0000 [thread overview]
Message-ID: <3F46378F.1000102@redhat.com> (raw)
In-Reply-To: <3F40F4BF.5020702@redhat.com>
>> This patch is the last major piece of fork tracing: support for vfork and
>> exec. I have not enabled the code in infrun which attempts to automatically
>> load the new executable, because I'm not happy with how it works, and
>> because it isn't necessary for this to be useful.
>>
>> I'll move this to the branch in a day or two if there are no problems.
>> I suppose fixing up the expected output in the testsuite is next...
>>
> Please don't. The only things I know of still going down for 6.0 are some testsuite mangling and a re-fix for the red zone.
>
> Anything else can go in 6.1.
>
> My core file stuff, for instance, isn't in 6.0.
Daniel,
I'm really disappointed by the situtation you've created here. You, by
at the last moment trying to add this new functionality to 6.0 branch,
have effectively pushed me into a corner. I've got the following choices:
- yank the existing code
invalidates relevant tests
as the release manager, I get the blame for delaying both the new
feature and the release
- leave the code as is
Again, I get the blame for the feature not being present (after all it
is just wafer thin and won't have any affect on all the test results
that people have been doing up-until now, right?)
- let the change in
invalidating test results
again delay the release ...
Against my better judgment, I've decided to go with option 3. You can
commit this change but the release is delayed an extra week.
I'm now also forced to consider a move away from self regulation and
instead require release manager approval for all branch changes. A
change that would benefit no one :-(
Andrew
next prev parent reply other threads:[~2003-08-22 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 20:19 Daniel Jacobowitz
2003-08-18 15:46 ` Andrew Cagney
2003-08-22 15:32 ` Andrew Cagney [this message]
2003-08-22 21:20 ` Daniel Jacobowitz
2003-08-22 15:53 Michael Elizabeth Chastain
2003-08-22 18:40 ` Andrew Cagney
2003-08-22 19:36 Michael Elizabeth Chastain
2003-08-22 22:07 ` Andrew Cagney
2003-08-25 1:19 Michael Elizabeth Chastain
2003-08-25 15:06 ` 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=3F46378F.1000102@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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