From: "Eli Zaretskii" <eliz@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: hilfingr@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Thu, 03 Jun 2004 04:30:00 -0000 [thread overview]
Message-ID: <9003-Thu03Jun2004072802+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040603041558.GI2319@gnat.com> (message from Joel Brobecker on Wed, 2 Jun 2004 21:15:58 -0700)
> Date: Wed, 2 Jun 2004 21:15:58 -0700
> From: Joel Brobecker <brobecker@gnat.com>
>
> This one is going to be tough.
``Tough'' because of the sheer volume of changes, or for some other
reason? (I understand that you didn't keep the logs of the changes
internally, is that right?)
Anyway, I realize that it would be a lot of work to write all the
entries now (although it's almost mechanichal work), but perhaps at
least the major changes could be described for specific functions, and
new functions could be described as such?
next prev parent reply other threads:[~2004-06-03 4:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2004-06-03 4:41 ` Joel Brobecker
2004-06-04 11:43 ` Eli Zaretskii
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
2004-06-05 14:26 Michael Elizabeth Chastain
2004-06-05 16:06 ` 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=9003-Thu03Jun2004072802+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.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