From: Eli Zaretskii <eliz@is.elta.co.il>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] abort() to internal_error()
Date: Wed, 21 Feb 2001 02:07:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010221120010.18287S@is> (raw)
In-Reply-To: <1010221065142.ZM27191@ocotillo.lan>
On Tue, 20 Feb 2001, Kevin Buettner wrote:
> * monitor.c (monitor_printf_noecho, monitor_printf,
> monitor_dump_regs): Likewise.
This is not how ChangeLog entries should span several lines; see
standards.texi. This style gets in the way of font-lock in Emacs, for
starters. It should be formatted like so:
* monitor.c (monitor_printf_noecho, monitor_printf)
(monitor_dump_regs): Likewise.
(Today seems like my nitpicking day; sorry about that ;-)
> * valprint.c (print_decimal, print_longest, print_longest,
> strcat_longest): Likewise.
Likewise.
next prev parent reply other threads:[~2001-02-21 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 22:51 Kevin Buettner
2001-02-20 23:14 ` Kevin Buettner
2001-02-21 2:07 ` Eli Zaretskii [this message]
2001-02-21 7:54 ` Kevin Buettner
2001-02-21 8:03 ` Eli Zaretskii
2001-02-21 8:46 ` Kevin Buettner
2001-02-21 9:09 ` Eli Zaretskii
2001-02-24 20:46 ` Kevin Buettner
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=Pine.SUN.3.91.1010221120010.18287S@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.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