>
> Basically, the VCS will ask you to type in a message describing each
> commit you make.  You simply have to format that message like you would
> an entry in a ChangeLog.


I guess you mean that git will ask to enter a commit message? So I did that,
but how does it get into the patch? (I am using magit, maybe I should check
out vc, which is what I am doing now)

The ChangeLog files are automatically generated from VCS history (your
> commit log entries) every time a release is made, AFAIK.
>

Indeed, I think I've read that somewhere .

Thanks!  Have you signed the copyright papers?
>

yes

You should read CONTRIBUTE, it details the procedure quite well.
>

good idea, I forgot about that document

On Tue, 11 Jan 2022 at 03:32, Po Lu <luangruo@yahoo.com> wrote:

> dalanicolai <dalanicolai@gmail.com> writes:
>
> > I've read the info about sending patches, however, I don't understand
> > the section about the changelog (it mentions that there is a changelog
> > or something, but it doesn't say where).
>
> > Also, the info tells us to write the commit log entries, but it does
> > not say where to do this.
>
> Basically, the VCS will ask you to type in a message describing each
> commit you make.  You simply have to format that message like you would
> an entry in a ChangeLog.
>
> > Looking at the changelog files, I guess that info is just really
> > outdated (am I right?).
>
> The ChangeLog files are automatically generated from VCS history (your
> commit log entries) every time a release is made, AFAIK.
>
> I hope I cleared up some things.
>
> > Anyway, the patch is in the attachment.
>
> Thanks!  Have you signed the copyright papers?
>
> > If there is some part of the 'protocol' that I did not understand then
> > please inform me about it.
>
> You should read CONTRIBUTE, it details the procedure quite well.
>