From: mike stump <mrs@windriver.com>
To: bosch@gnat.com
Cc: gcc@gcc.gnu.org, jsm28@cam.ac.uk
Subject: Re: Ada documentation issues
Date: Fri, 05 Oct 2001 15:33:00 -0000 [thread overview]
Message-ID: <200110052233.PAA18646@kankakee.wrs.com> (raw)
> Date: Fri, 5 Oct 2001 17:48:27 -0400 (EDT)
> From: Geert Bosch <bosch@gnat.com>
> To: mike stump <mrs@windriver.com>
> Cc: jsm28@cam.ac.uk, gcc@gcc.gnu.org
> I'd like to have a somewhat better log than "merged in changes", but
> maybe that will be too hard.
The ChangeLog file can be as complete and featureful as you want..
Also, if you run it nightly, in the cvs ci command, you can include
The top hunk of the changelog. Also, in the ChangeLog, you should not
have a comment like, merged in bla...
next reply other threads:[~2001-10-05 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 15:33 mike stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 8:27 dewar
2001-10-06 8:17 dewar
2001-10-05 14:41 mike stump
2001-10-05 14:48 ` Geert Bosch
2001-10-05 15:23 ` Joseph S. Myers
2001-10-05 14:01 Joseph S. Myers
2001-10-05 14:27 ` Geert Bosch
2001-10-09 4:14 ` Gerald Pfeifer
2001-10-09 4:20 ` Joseph S. Myers
2001-10-09 11:37 ` Gerald Pfeifer
2001-10-09 11:39 ` Geert Bosch
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=200110052233.PAA18646@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).