From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: Pending breakpoints and scripts
Date: Mon, 09 Feb 2004 22:38:00 -0000 [thread overview]
Message-ID: <40280BE4.2010003@gnu.org> (raw)
In-Reply-To: <20040209222738.3E6D34B363@berman.michael-chastain.com>
> Thoughts?
>
>
> You might not agree with this thought ... push back the branch cut until
> there haven't been any new "breakpoint pending" issues surfaced for a
> week.
>
> (Kind of a brutal thought, I know)
Well, looking at the math:
- I post the enable tui patch today (...)
- wait a week
- I commit the enable tui patch (which will make a mess)
- wait a week
- branch
that puts the branch at ~22.
I think enabling the TUI will make this breakpoint stuff look like a ripple.
(I'm obviously going to have to commit the TUI stuff earlier :-/)
Andrew
next prev parent reply other threads:[~2004-02-09 22:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 22:27 Michael Elizabeth Chastain
2004-02-09 22:38 ` Andrew Cagney [this message]
2004-02-10 6:33 ` New command MuthuKumar-Hotpop
2004-02-10 6:36 ` Kip Macy
2004-02-10 7:07 ` MuthuKumar-Hotpop
-- strict thread matches above, loose matches on Subject: below --
2004-02-09 20:02 Pending breakpoints and scripts Andrew Cagney
2004-02-09 22:32 ` Daniel Jacobowitz
2004-02-10 21:22 ` Andrew Cagney
2004-02-10 22:26 ` Daniel Jacobowitz
2004-02-11 14:31 ` Andrew Cagney
2004-02-11 14:47 ` Daniel Jacobowitz
2004-02-17 19:24 ` Andrew Cagney
2004-02-17 19:31 ` Daniel Jacobowitz
2004-02-17 19:39 ` Andrew Cagney
2004-02-17 19:41 ` Daniel Jacobowitz
2004-02-17 20:07 ` Jeff Johnston
2004-02-17 20:14 ` Andrew Cagney
2004-02-17 20:15 ` Daniel Jacobowitz
2004-02-17 20:13 ` Andrew Cagney
2004-02-17 20:15 ` Daniel Jacobowitz
2004-02-17 20:30 ` Andrew Cagney
2004-02-17 20:35 ` 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=40280BE4.2010003@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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