Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: gdb-patches@sources.redhat.com, uweigand@de.ibm.com
Subject: Re: [PATCH] S/390 port modernization - revised 4/4
Date: Tue, 20 Jan 2004 19:56:00 -0000	[thread overview]
Message-ID: <vt2llo2xumb.fsf@zenia.home> (raw)
In-Reply-To: <200401191931.UAA02622@faui1d.informatik.uni-erlangen.de>


Assuming these four revised patches introduce no new ARI hits, they're
approved.  There is only one change I'd like to see, to the log
entries.

> ChangeLog:
> 
...
> 	(op_*, op1_*, op2_* enums): Add several new opcodes.

It's best never to use wildcards in ChangeLog entries.  People don't
read the ChangeLog from start to end (or end to start); they search
for entries that refer to the item they're trying to understand.

I think the ChangeLog entry should specifically list those op* values
that were added:

        (op1_ag, op1_ay, op1_brasl, op1_brc, op1_brcl, op1_lay, op1_lg)
        (op1_lmy, op1_ly, op1_sg, op1_stmy, op1_sty, op1_sy, op_a)
        (op_agr, op_bas, op_bc, op_bcr, op_sgr, op_sr): New opcodes.

I see there were none removed, or significantly changed.

If this is inconvenient for you, I can make the change after your
patch is committed.


  reply	other threads:[~2004-01-20 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 19:31 Ulrich Weigand
2004-01-20 19:56 ` Jim Blandy [this message]
2004-01-20 20:31   ` Ulrich Weigand
2004-01-22  4:34     ` Jim Blandy
2004-01-23 14:58 Ulrich Weigand

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=vt2llo2xumb.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=uweigand@de.ibm.com \
    --cc=weigand@i1.informatik.uni-erlangen.de \
    /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