From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, Paul Hilfinger <hilfingr@gnat.com>
Cc: mec.gnu@mindspring.com, brobecker@gnat.com,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Mon, 07 Jun 2004 13:40:00 -0000 [thread overview]
Message-ID: <40C4703E.7040308@gnu.org> (raw)
In-Reply-To: <5567-Sun06Jun2004070516+0300-eliz@gnu.org>
>>From: Paul Hilfinger <hilfingr@gnat.com>
>>> Date: Sat, 5 Jun 2004 19:15:12 -0400 (EDT)
>>>
>>> If what Andrew
>>> wants is a list of exported functions, or even a list of all functions
>>> in the ada* files, we can certainly provide that. If he wants
>>> ChangeLog entries for differences between the old versions of the ada*
>>> files in the CVS repository and the ones we just deposited, we can
>>> provide that easily enough also
>
>
> I think we want the latter.
Yes, the ChangeLog just and always needs to reflect what was changed.
This is accepted best pratice, and has nothing to do with what `he
wants' :-/
Andrew
next prev parent reply other threads:[~2004-06-07 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 5:12 Michael Elizabeth Chastain
2004-06-03 7:05 ` Paul Hilfinger
2004-06-04 11:45 ` Eli Zaretskii
2004-06-04 18:32 ` Andrew Cagney
2004-06-04 18:37 ` Joel Brobecker
2004-06-04 18:55 ` Daniel Jacobowitz
2004-06-04 19:10 ` Andrew Cagney
2004-06-05 10:11 ` Eli Zaretskii
2004-06-05 13:33 ` Andrew Cagney
2004-06-05 16:07 ` Eli Zaretskii
2004-06-05 23:15 ` Paul Hilfinger
2004-06-06 4:08 ` Eli Zaretskii
2004-06-07 13:40 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-05 14:26 Michael Elizabeth Chastain
2004-06-05 16:06 ` Eli Zaretskii
2004-06-02 10:03 Paul Hilfinger
2004-06-03 4:06 ` Eli Zaretskii
2004-06-03 4:16 ` Joel Brobecker
2004-06-03 4:30 ` Eli Zaretskii
2004-06-03 4:41 ` Joel Brobecker
2004-06-04 11:43 ` 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=40C4703E.7040308@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.com \
--cc=mec.gnu@mindspring.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