This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH]: Updates to Ada sources, part 1 (longish)


Date: Thu, 3 Jun 2004 01:12:28 -0400 (EDT)
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)

Speaking as a consumer of ChangeLogs, I would favor just importing
ChangeLog.GNAT into the FSF repository, with a note at the top of
it saying "these are changes from $date to $date done by ACT and
merged on 2004-06-02."


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.

An alternative idea is to put the contents of ChangeLog.GNAT into
gdb/ChangeLog, but indent it so that the date/time stamps of the
included ChangeLog.GNAT are not aligned with the rest of time stamps,
and thus the time monotonicity is not disrupted.  I think the Texinfo
project did that in the past when large changes were merged that were
maintained separately for some time.

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?


Much of the stuff in that GNAT ChangeLog will no longer be relevant. I'm told Diego took rougly a day to prepare his tree-SSA ChangeLog entry.

(BTW, with a change of this magnitude it is probably a good idea to table it for a day or so)

enjoy,
Andrew




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]