From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: mec.gnu@mindspring.com, brobecker@gnat.com, hilfingr@gnat.com,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Sat, 05 Jun 2004 10:11:00 -0000 [thread overview]
Message-ID: <9743-Sat05Jun2004130832+0300-eliz@gnu.org> (raw)
In-Reply-To: <40C0C01D.7080504@gnu.org> (message from Andrew Cagney on Fri, 04 Jun 2004 14:31:57 -0400)
> Date: Fri, 04 Jun 2004 14:31:57 -0400
> From: Andrew Cagney <cagney@gnu.org>
> >
> > That'd be fine with me, but I'd also suggest to have a pointer to
> > ChangeLog.GNAT in gdb/ChangeLog, right where the import of Ada changes
> > is recorded. Something like "See ChangeLog.GNAT for details of the
> > changes."
>
> Please don't do this. ChangeLog.XXX is good for branches (as with even
> readline/ChangeLog.gdb) but not for what is ment to be the mainline.
I agree with the principle, but I don't think it is such a sacred one
that would justify asking the GNAT people to invest such a large
effort.
We need the information to be there, and the suggested compromises
achieve that with a reasonable effort.
> The ChangeLog entry should provide a summary of what was added/changed
> at this point in time - stuff like listing the new functions and summary
> of changed functions. Can we do that?
How many man-hours would you say is reasonable for such an effort?
1? 10? 100? 1000? Where, if at all, do we draw the line?
> Much of the stuff in that GNAT ChangeLog will no longer be relevant.
I understand that the problem is to translate the irrelevant suff into
something that is relevant. I suggested that at first, but the GNAT
people tell that it will take a lot of work.
> I'm told Diego took rougly a day to prepare his tree-SSA ChangeLog entry.
Who is Diego and how is the tree-SSA stuff relevant to our case?
next prev parent reply other threads:[~2004-06-05 10:11 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 [this message]
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
-- 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=9743-Sat05Jun2004130832+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@gnat.com \
--cc=cagney@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