GNU bug report logs - #66554
[PATCH] Add the public API of Compat to the core

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: mail <at> daniel-mendler.de, stefankangas <at> gmail.com, monnier <at> iro.umontreal.ca, 66554 <at> debbugs.gnu.org
Subject: bug#66554: [PATCH] Add the public API of Compat to the core
Date: Fri, 12 Jan 2024 09:32:17 +0200

> From: Philip Kaludercic <philipk <at> posteo.net>
> Cc: Daniel Mendler <mail <at> daniel-mendler.de>,  66554 <at> debbugs.gnu.org,
>   eliz <at> gnu.org,  Stefan Kangas <stefankangas <at> gmail.com>
> Date: Thu, 11 Jan 2024 20:24:25 +0000
> 
> > The addition cab done procedurally, as in
> >
> >     ;;;;####autoload (push (list 'compat emacs-major-version
> > emacs-minor-version) package--builtin-versions)
> 
> If this work, I like this idea a lot!  I'll test it out to see if this
> could simplify things.

I'm not sure I understand the effects of the above -- can you explain?

In general, if something needs to be done when the Emacs version is
bumped, that action should be described in make-tarball.txt.  It is a
nuisance to follow the procedure there, only to be reminded of
something else via a warning emitted by the build (and that is even
before we consider the possibility that someone launches a build and
goes for a coffee, while the warnings scroll on the screen with no one
to see them).  Likewise, if a file is modified by whatever commands we
invoke to bump an Emacs version, that file should be mentioned in
make-tarball.txt, because the person who performs that procedure will
then need to commit the changes with a suitable log message, like we
do today with configure.ac and the rest. 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.