Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Omair Javaid <omair.javaid@linaro.org>
Cc: oza Pawandeep <oza.pawandeep@gmail.com>,
	Yao Qi <yao@codesourcery.com>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	       patches <patches@linaro.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH 0/2] GDB process record and reverse debugging improvements for arm*-linux*
Date: Fri, 20 Dec 2013 12:38:00 -0000	[thread overview]
Message-ID: <52B43A57.7050705@redhat.com> (raw)
In-Reply-To: <52929058.1050202@linaro.org>

On 11/24/2013 11:48 PM, Omair Javaid wrote:

> After incorporating all suggestions I am posting a final version of all 
> three patches posted earlier. Looking for a go ahead for commit.

All three emails in the series have the same subject apart from
the numbers, which make it confusing.  It'd be good if you made
sure the subjects were actually different, and more specific,
in the git commit log.

Hmm, I'm also surprised to now find that this "0/2" email
actually contains a patch.  That makes it actually 3 patches
in the series.  This is not the standard de facto way to
send a series.  The best way is for 0 to be the series intro,
with no patch, and then have the patches be replies to the
intro mail.  (I'd suggest addressing the comments I just
sent to patches #1 and #2, and resend the whole series with
git send-mail, which does that for you automatically.)

> 
> == PATCH 0 ==
> 
> This patch adds a news entry about improved process record-replay on
> arm*-linux* targets.
> It also adds linux-record.o to gdb_target_obs in configure.tgt and
> enables gdb.reverse testsuite for arm*-linux* targets.

These could be two separate patches, with NEWS actually being the
last patch in the whole series.

> gdb/testsuite:
> 
> 2013-10-24  Omair Javaid  <omair.javaid@linaro.org>
> 
> 	* lib/gdb.exp: Enable gdb.reverse testsuite for arm*-linux* targets.

Write:

 	* lib/gdb.exp (supports_process_record): Return true for arm*-linux*.

Otherwise looks good.

-- 
Pedro Alves


  parent reply	other threads:[~2013-12-20 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  0:09 Omair Javaid
2013-10-24  1:42 ` Yao Qi
2013-10-24  1:44 ` Yao Qi
2013-11-08  3:20   ` Omair Javaid
2013-11-08  8:04     ` Eli Zaretskii
2013-11-08  8:21       ` oza Pawandeep
2013-11-11  8:25         ` Omair Javaid
2013-11-24 23:49           ` Omair Javaid
2013-11-25  4:56             ` Eli Zaretskii
2013-12-17 10:22               ` Omair Javaid
2013-12-20 12:38             ` Pedro Alves [this message]
2014-01-03 19:20               ` Omair Javaid

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=52B43A57.7050705@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=omair.javaid@linaro.org \
    --cc=oza.pawandeep@gmail.com \
    --cc=patches@linaro.org \
    --cc=yao@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