On Sat, Oct 22, 2022 at 05:47:32PM +0200, Tony Mechelynck wrote:
> At least on the Mercurial server, patch 9.0.815 has no description of
> the "problem", nor of the "solution", and it also hasn't got a
> Mercurial tag.

Same on the Git server.

Also, the v9.0.0814 tag points to the same commit as v9.0.0813, and the
actual 9.0.0814 commit is untagged.

> Neither does it have a vim-dev message AFAICT.

I haven't seen one.  But I have seen the segfaults introduced by it.

Marius Gedminas
-- 
/* Intel provided a special instruction to clear the TS bit for people too cool
 * to use write_cr0() to do it.  This "clts" instruction is faster, because all
 * the vowels have been optimized out. */
                -- lguest source code

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20221022190307.4ci3j7yvgkwmwf4z%40blynas.

Attachment: signature.asc
Description: PGP signature

Raspunde prin e-mail lui