From: Daniel Berlin <dan@cgsoftware.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: Christopher Blizzard <blizzard@mozilla.org>,
gdb-patches@sourceware.cygnus.com
Subject: Re: [Fwd: gdb patch]
Date: Mon, 08 May 2000 14:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10005081446080.19102-100000@propylaea.anduin.com> (raw)
In-Reply-To: <3916E7CF.6975@cygnus.com>
It breaks quite a lot as default, because it always centers on the
context, even if you try to pass other options.
As an option (IE how it is now, list -w), it breaks nothing.
--Dan
>
> The general consensus is that it is a good thing, but there is
> concern that it might break test suites. The last word on the
> subject that I remember was that Daniel did not believe that
> it would break test suites, and he was gonna go verify this.
>
> Michael
next prev parent reply other threads:[~2000-05-08 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3916DC7C.D17FE386@mozilla.org>
2000-05-08 9:16 ` Michael Snyder
2000-05-08 14:47 ` Daniel Berlin [this message]
2000-05-08 14:50 ` Michael Snyder
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=Pine.LNX.4.10.10005081446080.19102-100000@propylaea.anduin.com \
--to=dan@cgsoftware.com \
--cc=blizzard@mozilla.org \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=msnyder@cygnus.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