Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ping: [patch] set logging {redirect|overwrite} warning
Date: Thu, 02 Sep 2010 16:51:00 -0000	[thread overview]
Message-ID: <20100902154242.GA8751@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <201009021611.21144.pedro@codesourcery.com>

On Thu, 02 Sep 2010 17:11:20 +0200, Pedro Alves wrote:
> On Thursday 02 September 2010 15:53:46, Jan Kratochvil wrote:
> > No regressions on {x86_64,x86_64-m32,i686}-fedora14snapshot-linux-gnu.
> > 
> > OK to check-in?
> 
> Okay, thanks.
> 
> > 2010-08-13  Jan Kratochvil  <jan.kratochvil@redhat.com>
> > 
> > 	* cli-logging.c: Include gdb_assert.h.
> > 	(set_logging_overwrite): New function.
> > 	(logging_redirect): New comment.
> > 	(logging_no_redirect_file, set_logging_redirect)
> > 	(pop_output_files) <logging_no_redirect_file>: New.
> > 	(handle_redirections) <!logging_redirect>: New variable
> > 	no_redirect_file.  Remove file autoclose for tee_file_new.  No longer
> > 	discard cleanup for the close of former OUTPUT.  Set
> > 	LOGGING_NO_REDIRECT_FILE.
> > 	(handle_redirections) <logging_redirect>: gdb_assert
> > 	LOGGING_NO_REDIRECT_FILE.
> > 	(show_logging_command) <logging_redirect handling>: Adjust messages
> > 	for SAVED_FILENAME not NULL.
> > 	(_initialize_cli_logging): Install set_logging_overwrite and
> > 	set_logging_redirect.

Checked-in:
	http://sourceware.org/ml/gdb-cvs/2010-09/msg00020.html


Thanks,
Jan


      reply	other threads:[~2010-09-02 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 18:29 Jan Kratochvil
2010-08-12 16:07 ` Pedro Alves
2010-08-13 21:56   ` Jan Kratochvil
2010-09-02 15:21     ` ping: " Jan Kratochvil
2010-09-02 15:36       ` Pedro Alves
2010-09-02 16:51         ` Jan Kratochvil [this message]

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=20100902154242.GA8751@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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