From: Eli Zaretskii <eliz@is.elta.co.il>
To: cgd@broadcom.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [applied mips sim patch] trace "d" shift instructions.
Date: Sun, 03 Mar 2002 03:53:00 -0000 [thread overview]
Message-ID: <200203031152.NAA00966@is.elta.co.il> (raw)
In-Reply-To: <yov5u1rzrht2.fsf@broadcom.com> (cgd@broadcom.com)
> From: cgd@broadcom.com
> Date: 01 Mar 2002 15:26:17 -0800
>
> ===================================================================
> 2002-03-01 Chris Demetriou <cgd@broadcom.com>
>
> * mips.igen (do_dsll, do_dsllv, DSLL32, do_dsra, DSRA32, do_dsrl,
> DSRL32, do_dsrlv): Trace inputs and results.
Just a quick note: this is not how ChangeLog entries that span several
lines should be formatted, according to standards.texi. You should do
it like this:
* mips.igen (do_dsll, do_dsllv, DSLL32, do_dsra, DSRA32, do_dsrl)
(DSRL32, do_dsrlv): Trace inputs and results.
That is, close the parens on each line and open them anew on the next
one. One reason for this format is that Emacs highlights parts of the
entries in different colors, and it depends on this format to DTRT.
Another reason is that it makes it easier to grep ChangeLog files for
function/variable names.
If you use Emacs 21.1 or later, the command "C-x 4 a", when typed
inside the function/variable definition for which you need to write a
ChangeLog entry, will do the above formatting automatically for you.
next prev parent reply other threads:[~2002-03-03 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 15:26 cgd
[not found] ` <mailpost.1015025187.23583@news-sj1-1>
2002-03-01 15:36 ` cgd
2002-03-03 3:53 ` Eli Zaretskii [this message]
2002-03-03 12:17 ` cgd
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=200203031152.NAA00966@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=cgd@broadcom.com \
--cc=gdb-patches@sources.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