On 29.06.22 12:33, oldk1331 wrote:
I'd like to discuss about the status of ChangeLog.
I don't like to include ChangeLog recently because my patches
are reviewed in undetermined order, with ChangeLog entries in
the patch, it will surely get merge/rebase conflict. Also the
date would be inaccurate.
That is also my opinion. The ChangeLog file is a needless complication
if we work with git and shuffle the order of commits during development.
One anyway gets everything with "git log" or the short form "git log
--oneline". There are even programs that generate nicer output.
Of course I can manually add ChangeLog entries after patch
review and before I commit it.
I think that is an unnessary burden and adds no benefit. The information
is just doubled from the commit message.
What can be done is to generate a ChangeLog for a release. However, in
recent commits Waldek anyway creates a list of entries for ug15.htex.
The information for that can be retrieved from "git log". We should make
sure that the log-messages are nice and say why a certain commit was
done. But there is no need for our current ChangeLog file anymore.
Ralf
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/bc8471cb-74b0-73e1-5faf-99752aaa462f%40hemmecke.org.
