Re: c-font-lock-extra-types and friends

[Alan Mackenzie <acm@muc.de>]

Hello, Eli.

On Mon, Mar 13, 2023 at 18:04:33 +0000, Alan Mackenzie wrote:
> On Mon, Mar 13, 2023 at 19:12:59 +0200, Eli Zaretskii wrote:
> > > Date: Mon, 13 Mar 2023 16:54:55 +0000
> > > Cc: emacs-devel@gnu.org
> > > From: Alan Mackenzie <acm@muc.de>

> > > Hello, Eli.

> > > On Sun, Mar 05, 2023 at 08:57:35 +0200, Eli Zaretskii wrote:
> > > > Every time I visit etags.c, I need to confirm the application of the
> > > > file-local vars, because c-font-lock-extra-types doesn't have the
> > > > appropriate safe-local-variable-p property.  Is there any reason not
> > > > to consider its value safe by default if it is a list of strings?

> > > I've committed a fix for this to master.  Would you possibly give it a
> > > quick test sometime, and confirm the job is done, please.

> > Thanks, but I think you forgot to push.

> Sorry.  I installed git 2.39.2 yesterday evening, and think I've hit a
> bug in it.  When I attempted to push, I got a message saying somebody
> else had pushed.  So I did a git pull --rebase, and found I no longer
> had any outstanding commits to push.  I assumed my push had somehow got
> through.

> At the moment, my main git repository has no outstanding commits to
> push, and seems to think my latest (non-)push is already pushed.

> Hopefully I can find a workaround for this discrepancy.

> Sorry again.

No, it was my fault.  For some reason, I was trying to push from the
wrong repository.  The commit should be in master now.

-- 
Alan Mackenzie (Nuremberg, Germany).