Re: Stop updating ChangeLog?

[Dmitry Samersoff <dms at samersoff dot net>]

Yao,

> c) If answer are Yes/No, developers still have to write changelog
> entries in git commit log, and we can generate ChangeLog on
> release from git log.

My version.

I use changelog to check what was changed in gdb. I can live with (c)
and get this information directly from git, but it requires some
additional efforts on my side.

-Dmitry

On 02/05/2018 07:00 PM, Yao Qi wrote:
> Hi all,
> The discussion in this thread
> https://sourceware.org/ml/gdb-patches/2018-02/msg00012.html
> leads to a discussion that whether we still need ChangeLog.  I start
> a new thread to get more attention on this topic.
> 
> In current development, we need to write one ore more changelog
> entries for each commit, put them into both git commit log and
> ChangeLog files.  How much we can change to existing mode
> depends the answers to these following questions,
> 
>  #1 Are ChangeLog files useful in GDB releases to various people
>  who build GDB releases?
>  #2 Are ChangeLog files useful in GDB repo to various GDB
>  developers?
> 
> a) If answers are Yes/Yes, we keep unchanged,
> b) If answers are No/No, we don't need to write changelog entries in
> git commit log, nor updating ChangeLog file,
> c) If answer are Yes/No, developers still have to write changelog
> entries in git commit log, and we can generate ChangeLog on
> release from git log.
> d) If answers are No/Yes, get use to git to get the information from
> git log instead of ChangeLog,
> 
> My answers are No/No, so I suggest that we do b).  I can live up with
> c), but that needs change in the release process.  What do you think?
> 


-- 
Dmitry Samersoff
http://devnull.samersoff.net
* There will come soft rains ...

Attachment: signature.asc
Description: OpenPGP digital signature