From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Fri, 04 Jun 2004 18:55:00 -0000 [thread overview]
Message-ID: <20040604185549.GA11036@nevyn.them.org> (raw)
In-Reply-To: <20040604183743.GL765@gnat.com>
On Fri, Jun 04, 2004 at 11:37:43AM -0700, Joel Brobecker wrote:
> > 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?
>
> What I was saying was that it's going to be a non-trivial amount of time
> to prepare that monster changelog entry. If you (the maintainers) think
> it is necessary then, fine, we'll do it. But I'd much rather see this
> time used to other things as I don't think the benefits of this
> particular task will outweight the cost. But it's the maintainers call.
Personally, I don't think it's worthwhile. These files are still not
built in the FSF tree. Until they are, I think they have the moral
equivalent of a changelog entry that says "New file". Once they are
built, naturally, they'll be change controlled like anything else.
Just my opinion.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-04 18:55 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 [this message]
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
-- 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=20040604185549.GA11036@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.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