Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <michsnyd@cisco.com>
Cc: gdb-patches@sources.redhat.com, msnyder@redhat.com
Subject: Re: [RFA] Linux Checkpoint/Restart, take 2
Date: Thu, 22 Dec 2005 13:20:00 -0000	[thread overview]
Message-ID: <uu0d3ebn5.fsf@gnu.org> (raw)
In-Reply-To: <43A777EE.50404@cisco.com> (message from Michael Snyder on Mon, 	19 Dec 2005 19:18:06 -0800)

> Date: Mon, 19 Dec 2005 19:18:06 -0800
> From: Michael Snyder <michsnyd@cisco.com>
> CC: msnyder@redhat.com
> 
> OK, superceding the previous submission, this patch includes
> suggested mods from Eli and Tom Tromey.  Fixed comment formatting,
> tweaked documentation, added NEWS and gdbint.texinfo.

Thanks!  The documentation patches can go in, provided that you take
care of the minor issues mentioned below.

> + @var{checkpoint-id}.  All program variables, registers, stack frames
> + etc.  will be returned to the values that they had when the checkpoint

Need a "@:" after "etc.", since it doesn't end a sentence.  For the
same reason, there need to be only one space after it, not two.

> + It won't ``un-write'' data from
> + a file, but it will rewind the file pointer to the previous location,

Really? isn't the file pointer stored inside some OS kernel data
structure?

> + from eg. a serial device can be removed from internal program buffers,

Pleased add "@:" after "eg." (actually, I believe we need to say
"e.g.").

> + in gdb, eg. as corefiles, as forked processes, and as some opaque

Same here.

> + Some targets, eg. simulators, might have their own built-in 

And here.

Thanks again for adding this great feature and for your efforts in
providing good documentation.


  reply	other threads:[~2005-12-20 20:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22  4:05 Michael Snyder
2005-12-22 13:20 ` Eli Zaretskii [this message]
2005-12-22 14:09   ` Michael Snyder
2005-12-22 14:20     ` Eli Zaretskii
2005-12-26 14:49     ` [commit] Fix "eg." and "e.g." in the docs (was: [RFA] Linux Checkpoint/Restart, take 2) Eli Zaretskii
2005-12-26 15:34     ` [commit] Fix usage of "etc." " Eli Zaretskii
2005-12-23 21:52   ` [RFA] Linux Checkpoint/Restart, take 2 Michael Snyder
2005-12-23 22:00     ` Eli Zaretskii
2005-12-23 22:42 ` Daniel Jacobowitz
2005-12-24 15:25   ` Michael Snyder
2005-12-24 15:30     ` Daniel Jacobowitz
2005-12-24 16:15   ` [RFA] Linux Checkpoint/Restart, take 2 (footnote) Michael Snyder
2005-12-24 16:31     ` 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=uu0d3ebn5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=michsnyd@cisco.com \
    --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