From: Paul Hilfinger <hilfingr@gnat.com>
To: eliz@gnu.org
Cc: cagney@gnu.org, mec.gnu@mindspring.com, brobecker@gnat.com,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Sat, 05 Jun 2004 23:15:00 -0000 [thread overview]
Message-ID: <20040605231512.1A979F2C05@nile.gnat.com> (raw)
In-Reply-To: <2427-Sat05Jun2004190137+0300-eliz@gnu.org>
> I would even be happy if the contributor would do that when prompted
> (I prompted them to begin with, remember?).
>
> However, I'm not sure we should insist on this given the contributor's
> reluctance to do that, when prompted. It is IMHO enough to have the
> required information readily available in the distribution; a separate
> file will achieve just that.
>
> > We're talking an hour or perhaphs two
>
> How is this consistent with the fact that tree-SSA merge required a
> full day of work to prepare the log entries?
We seem to have started somewhat more of a debate than we intended
here. Our main reluctance about "preparing a full ChangeLog entry"
was simply that it was not at all clear what this meant. Redacting
each of our entries (going back to March 1997) so as to remove
irrelevant items---which is one interpretation of "complete
ChangeLog"---seemed a totally pointless waste of time. 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 (it would simply be a redacted version
of our own change log entries going back to the time we deposited
those files). In that case, Andrew, am I to understand that you don't
care about our internal change history prior to that point?
Paul Hilfinger
next prev parent reply other threads:[~2004-06-05 23:15 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 [this message]
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=20040605231512.1A979F2C05@nile.gnat.com \
--to=hilfingr@gnat.com \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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