public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] checkpoint: print index of new checkpoint in response message
Date: Sun, 23 Nov 2014 09:46:00 -0000	[thread overview]
Message-ID: <20141123094623.GD7136@adacore.com> (raw)
In-Reply-To: <1415991890-26872-1-git-send-email-patrick@parcs.ath.cx>

> This way the user can know the index of the latest checkpoint without
> having to run "info checkpoints" afterwards.
> 
> 2014-11-14  Patrick Palka  <patrick@parcs.ath.cx>
> 
> 	* linux-fork.c (checkpoint_command): Print index of new
> 	checkpoint in response message.

Looks good.

I will push this patch for you, but perhaps it might be time
for you to request "Write After Approval" privileges, allow you
to push your patches yourself. Let me know if you'd like to get
set up for that.

Thank you,
-- 
Joel

  parent reply	other threads:[~2014-11-23  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 19:05 Patrick Palka
2014-11-22 20:55 ` Patrick Palka
2014-11-23  9:46 ` Joel Brobecker [this message]
2014-11-23 12:46   ` Patrick Palka

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=20141123094623.GD7136@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=patrick@parcs.ath.cx \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).