--
--
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 vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3De52bn9Hfip8VAs2N%3DNTEhNTjHkSkyzp0TKfpuiiPz4Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/5a13bf47-b642-4224-b40b-41a454cff433n%40googlegroups.com.
Ken,
Please go ahead with enabling discussions and requesting admin rights. They may or may not be redirected, don't know yet, we will see.
Thanks
Chris
Am 06.08.2023 um 08:39 schrieb Ken Takata <ktakat...@gmail.com>:
--
--
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 vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/d71778b7-7e2c-44d7-b938-fadee2c8b9e9n%40googlegroups.com.
--
--
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 vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_g2KEkqcYo46BkEGxqNR_x%2Bypuj0AquFaF638d97vaEjA%40mail.gmail.com.
About point #9 i.e. "Incorporating the runtime file updates"
I've always found it odd that some changes were split into
a commit in src and another commit later in runtime. It
often caused confusion, with PR author asking "part of
my change was not included?!" and the response being
"it will be in the next runtime update". Perhaps that's
something worth revisiting?
There might also be other unrelated changes
which were pending in the next runtime update
that never happened. Often Bram responded
with "I'll include it" when people reported
corrections to the docs for example.
On Di, 08 Aug 2023, Yegappan Lakshmanan wrote:
> I am not suggesting a separate minor release for each runtime file update here.
> Otherwise, we will have too many minor releases. Can we make a minor release
> only for PRs that change the C code and not the runtime files (still
> merge the runtime changes as separate PRs)?
Yes, that should be possible. We can merge runtime files directly,
without incrementing the minor patch number and only increment the minor
patch number for changes to the source (including diff, libvterm, xxd or
the test suite)