From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <estetus@gmail.com> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit 0/3] Fix sysprof error on stop not started sysprof Date: Wed, 12 Mar 2025 14:11:29 +0300 [thread overview] Message-ID: <Z9Fr4Xb3Y1cmVHzZ@root> (raw) In-Reply-To: <cover.1740468394.git.sergeyb@tarantool.org> Sergey, I've applied the patch set into all long-term branches in tarantool/luajit and bumped a new version in master [1], release/3.3 [2], release/3.2 [3] and release/2.11 [4]. [1]: https://github.com/tarantool/tarantool/pull/11235 [2]: https://github.com/tarantool/tarantool/pull/11236 [3]: https://github.com/tarantool/tarantool/pull/11237 [4]: https://github.com/tarantool/tarantool/pull/11238 -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2025-03-12 11:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-25 7:32 Sergey Bronnikov via Tarantool-patches 2025-02-25 7:32 ` [Tarantool-patches] [PATCH luajit 1/3] sysprof: rename sysprof_error to prof_error Sergey Bronnikov via Tarantool-patches 2025-03-05 14:28 ` Sergey Kaplun via Tarantool-patches 2025-02-25 7:32 ` [Tarantool-patches] [PATCH luajit 2/3] misc: use prof_error for handling errors Sergey Bronnikov via Tarantool-patches 2025-03-05 14:49 ` Sergey Kaplun via Tarantool-patches 2025-03-06 16:04 ` Sergey Bronnikov via Tarantool-patches 2025-02-25 7:32 ` [Tarantool-patches] [PATCH luajit 3/3] sysprof: fix a message with stop without run Sergey Bronnikov via Tarantool-patches 2025-03-05 14:52 ` Sergey Kaplun via Tarantool-patches 2025-03-06 15:18 ` Sergey Bronnikov via Tarantool-patches 2025-03-12 11:11 ` Sergey Kaplun via Tarantool-patches [this message] 2025-03-06 16:18 [Tarantool-patches] [PATCH luajit 0/3] Fix sysprof error on stop not started sysprof Sergey Bronnikov via Tarantool-patches
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=Z9Fr4Xb3Y1cmVHzZ@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 0/3] Fix sysprof error on stop not started sysprof' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox