From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>, Hilfinger@CS.Berkeley.EDU
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] patch to remove language-dependent numeric output support
Date: Sun, 12 Sep 2004 15:53:00 -0000 [thread overview]
Message-ID: <41447052.10605@gnu.org> (raw)
In-Reply-To: <20040911035023.GA3631@nevyn.them.org>
> On Fri, Sep 10, 2004 at 07:40:32PM -0700, Paul Hilfinger wrote:
>
>>>
>>> > Just some notes though:
>>> > > (local_decimal_format_custom): Remove.
>>> > >
>>> > > * utils.c: (int_string): New function.
>>> > I suspect that the the blank lines aren't needed - blank lines separate
>>> > commits rather than separate parts of the same commit - whichever.
>>>
>>> Really? OK. Actually, I was putting in blank lines just to break up
>>> a long ChangeLog entry, but if there's actually a convention, I'm
>>> happy to follow it.
Near enough. Here's the exact text:
http://www.gnu.org/prep/standards_42.html#SEC42
> Separate unrelated change log entries with blank lines. When two entries represent parts of the same change, so that they work together, then don't put blank lines between them. Then you can omit the file name and the asterisk when successive entries are in the same file.
> FWIW, I've always used blank lines to separate logically distinct
> portions of a changelog entry. I have no idea what the actual
> convention is :-)
Or this. It has the same effect - we never combine logically distinct
changes into a single commit.
Andrew
next prev parent reply other threads:[~2004-09-12 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 0:38 Paul Hilfinger
2004-09-11 2:03 ` Andrew Cagney
2004-09-11 2:40 ` Paul Hilfinger
2004-09-11 3:50 ` Daniel Jacobowitz
2004-09-12 15:53 ` Andrew Cagney [this message]
2004-09-11 10:29 ` Paul Hilfinger
2004-09-11 11:32 ` Eli Zaretskii
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=41447052.10605@gnu.org \
--to=cagney@gnu.org \
--cc=Hilfinger@CS.Berkeley.EDU \
--cc=drow@false.org \
--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