> 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
Well if there was no message either use the info i"ll send later when I am
back home. I at first did not have them properly in git. Found the problem
in th third while working on the second.
On Sat, Oct 22, 2022, 16:47 Tony Mechelynck
wrote:
> At least on the Mercurial server, patch 9.0.815 has
I suppose the script that prepares the commit was missing a quote. Just
add the info from the email.
On Sat, Oct 22, 2022, 16:47 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
>
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
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.
Neither does it have a vim-dev message AFAICT.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
