On Sun, Jul 22, 2018 at 3:18 PM, Robert Pluim <rpluim@gmail.com> wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Robert Pluim <rpluim@gmail.com>
> >> Gmane-Reply-To-List: yes
> >> Date: Sun, 22 Jul 2018 12:16:48 +0200
> >> Cc: João Távora <joaotavora@gmail.com>
> >>
> >> joaotavora@gmail.com (João Távora) writes:
> >>
> >> > +your program and keep a change log.  In these situations, you may not
> >> > +want to keep a separate versioned change log file.  If
> >> > +@code{add-log-dont-create-changelog-file} is non-@code{nil},
> commands
> >> > +like @kbd{C-x 4 a} (@code{add-change-log-entry-other-window}) will
> >> > +record changes in a suitably named temporary buffer instead of a
> file,
> >> > +unless such a file already exists.
> >>
> >> So if add-log-dont-create-changelog-file is t, but ChangeLog exists as
> >> a file on disk, the entry goes there and not in the non-file ChangeLog
> >> buffer?
> >
> > Yes.
> >
> >> That would be surprising to me.
> >
> > Why surprising?  First, this is the current behavior, so this way we
> > are less incompatible; and second, that's why the option has "create"
> > in its name.
> >
> > Maybe I'm missing something.
>
> It has create, but it also has 'dont'. I guess I can see how it makes
> sense if you already have a ChangeLog file lying around.
>
> Anyway, I donʼt think I feel strongly enough about this to suggest a
> change.
>

It could be add-log-dont-create-new-changelog-file which maybe
would confuse even less people.

Feel free to change it, or don't, if it's not that big a deal.

João