From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: c-font-lock-extra-types and friends
Date: Mon, 13 Mar 2023 18:04:33 +0000 [thread overview]
Message-ID: <ZA9lsSIUt8ztbRzT@ACM> (raw)
In-Reply-To: <83zg8gshgk.fsf@gnu.org>
Hello, Eli.
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.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-03-13 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 6:57 c-font-lock-extra-types and friends Eli Zaretskii
2023-03-06 12:27 ` Alan Mackenzie
2023-03-09 9:47 ` Francesco Potortì
2023-03-13 16:54 ` Alan Mackenzie
2023-03-13 17:12 ` Eli Zaretskii
2023-03-13 18:04 ` Alan Mackenzie [this message]
2023-03-13 18:37 ` Alan Mackenzie
2023-03-14 12:25 ` Eli Zaretskii
2023-03-14 19:51 ` Eli Zaretskii
2023-03-18 6:40 ` Eli Zaretskii
2023-03-18 9:14 ` Alan Mackenzie
2023-03-18 9:35 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZA9lsSIUt8ztbRzT@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).