On Tue, Dec 12, 2023 at 8:41 AM Christian Brabandt <[email protected]> wrote: > > > On Di, 12 Dez 2023, Tony Mechelynck wrote: > > > Something has gone wrong again. > > > > Remember: tags v9.0.2140 to v9.0.2142 had gone missing, but tags > > v9.0.2143 to v9.0.2155 had been set correctly. Well, now tags > > v9.0.2156 to v9.0.2158 have gone missing again. > > > > This concerns only the Mercurial .hgtags metadata (and I don't know > > about any git metadata). In all cases the src/version.c contains the > > full list of patch numbers. > > Fixed. Not sure why this happened, the script did not receive a tag when > processing the git revision. This could happen, if I push out a new > patch, then the hg-bridge runs and a few moments later the tag is > pushed. However, this shouldn't happen 3 times in a row, so it's a bit > mysterious.
IOW, a race condition between the git commit and the hg fetch (or whatever it is called). Let's hope your fix catches it in the future. I'll keep eyes peeled in any case. > > I added some extra logic to parse the subject line in addition when this > happens again. > > Thanks, > Christian My pleasure, Tony. -- -- 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/CAJkCKXu0Hz8SaRH5TGWjmkNVdVy4P%3DVrcoegwb9ZVkcJFy6O4g%40mail.gmail.com.
