From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: "set logging"
Date: Sat, 28 Jun 2003 16:34:00 -0000 [thread overview]
Message-ID: <20030628163402.GA9716@nevyn.them.org> (raw)
In-Reply-To: <20030623214822.GA12881@nevyn.them.org>
On Mon, Jun 23, 2003 at 05:48:22PM -0400, Daniel Jacobowitz wrote:
> On Sun, Jun 22, 2003 at 04:53:22PM -0400, Daniel Jacobowitz wrote:
> > As discussed earlier:
> > set logging on [FILE]
> > set logging off
> > set logging overwrite [I changed the default to append]
> > set logging redirect
> > set logging file
> > show logging
> >
> > I decided that one-off command logging was really a different class of thing
> > from this patch, which is straight output logging, not really script-useful
> > redirection. So that's gone.
> >
> > Is this OK? Any comments? Docs OK?
>
> Here's an update, based on feedback. Barring comments I'll commit it
> in a couple of days to mainline, and next week to the branch.
Feedback was positive, so it's in. I'll put it on the branch next week
unless someone finds a problem.
I'm flushing my 6.0 queue... I only have one more significant issue,
but it will be a little while before I can get adequate test cases
together. Still waiting for comments on the MI testsuite patch.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-28 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 20:53 Daniel Jacobowitz
2003-06-22 21:33 ` Andrew Cagney
2003-06-22 23:57 ` Doug Evans
2003-06-23 0:15 ` Daniel Jacobowitz
2003-06-23 4:51 ` Eli Zaretskii
2003-06-23 22:15 ` Daniel Jacobowitz
2003-06-23 23:09 ` Andrew Cagney
2003-06-24 4:10 ` Eli Zaretskii
2003-06-28 16:34 ` Daniel Jacobowitz [this message]
2003-07-02 20:53 ` 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=20030628163402.GA9716@nevyn.them.org \
--to=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