Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@redhat.com>,
	gdb-patches@sources.redhat.com,         mark.kettenis@xs4all.nl
Subject: Re: [RFA] Linux Checkpoints, take 3
Date: Mon, 26 Dec 2005 19:27:00 -0000	[thread overview]
Message-ID: <ulkyazcd3.fsf@gnu.org> (raw)
In-Reply-To: <20051224161331.GA11718@nevyn.them.org> (message from Daniel 	Jacobowitz on Sat, 24 Dec 2005 11:13:32 -0500)

> Date: Sat, 24 Dec 2005 11:13:32 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com,
> 	mark.kettenis@xs4all.nl
> 
> On Sat, Dec 24, 2005 at 10:07:14AM +0200, Eli Zaretskii wrote:
> > > !       /* Detach new forked process?  */
> > > !       if (detach_fork)
> > >   	{
> > > ! 	  if (debug_linux_nat)
> > > ! 	    {
> > > ! 	      target_terminal_ours ();
> > > ! 	      fprintf_filtered (gdb_stdlog,
> > > ! 				"Detaching after fork from child process %d.\n",
> > > ! 				child_pid);
> > > ! 	    }
> > 
> > Might as well mark strings with _(), as long as we are changing the
> > code.
> 
> We've discussed this before, but I don't remember the conclusion - is
> there benefit to translating debug messages not intended for users?

Sorry, I don't remember either.  If we decided not to translate them,
then please disregard this my comment.


  reply	other threads:[~2005-12-24 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-24 16:32 Michael Snyder
2005-12-24 17:02 ` Eli Zaretskii
2005-12-26 18:58   ` Daniel Jacobowitz
2005-12-26 19:27     ` Eli Zaretskii [this message]
2005-12-27 15:38 ` Mark Kettenis
2005-12-27 15:40   ` Eli Zaretskii
2006-01-03 23:54   ` Michael Snyder
2006-01-04 19:16     ` Mark Kettenis
2006-01-04 19:36       ` Michael Snyder
2006-01-04  1:49   ` 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=ulkyazcd3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=msnyder@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