From: Maxim Kokryashkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: tarantool-patches@dev.tarantool.org, skaplun@tarantool.org,
sergeyb@tarantool.org
Subject: [Tarantool-patches] [PATCH luajit v3 1/6] build: purge sysprof.collapse module
Date: Wed, 13 Mar 2024 17:40:13 +0300 [thread overview]
Message-ID: <fe7ac994b4082938d2edbda3051dadb857529a42.1710340671.git.m.kokryashkin@tarantool.org> (raw)
In-Reply-To: <cover.1710340671.git.m.kokryashkin@tarantool.org>
This module became unused as a result of commit
tarantool/tarantool@e2851883cd4c23d41bd9aec23fad06fd10d39c45,
so it can be purged safely from the LuaJIT sources.
Part of tarantool/tarantool#8700
---
tools/CMakeLists.txt | 6 ------
tools/sysprof/collapse.lua | 3 ---
2 files changed, 9 deletions(-)
delete mode 100755 tools/sysprof/collapse.lua
diff --git a/tools/CMakeLists.txt b/tools/CMakeLists.txt
index b951f767..1dfc39e4 100644
--- a/tools/CMakeLists.txt
+++ b/tools/CMakeLists.txt
@@ -60,9 +60,6 @@ if(LUAJIT_DISABLE_SYSPROF)
else()
add_custom_target(tools-parse-sysprof EXCLUDE_FROM_ALL DEPENDS
sysprof/parse.lua
- # TODO: This line is not deleted only for the sake of integrational
- # testing. It should be deleted in the next series.
- sysprof/collapse.lua
sysprof.lua
utils/bufread.lua
utils/symtab.lua
@@ -71,9 +68,6 @@ else()
install(FILES
${CMAKE_CURRENT_SOURCE_DIR}/sysprof/parse.lua
- # TODO: This line is not deleted only for the sake of integrational
- # testing. It should be deleted in the next series.
- ${CMAKE_CURRENT_SOURCE_DIR}/sysprof/collapse.lua
DESTINATION ${LUAJIT_DATAROOTDIR}/sysprof
PERMISSIONS
OWNER_READ OWNER_WRITE
diff --git a/tools/sysprof/collapse.lua b/tools/sysprof/collapse.lua
deleted file mode 100755
index cac92f1a..00000000
--- a/tools/sysprof/collapse.lua
+++ /dev/null
@@ -1,3 +0,0 @@
--- FIXME: This file is not deleted only for the sake of
--- integrational testing. It should be deleted in the
--- next series.
--
2.44.0
next prev parent reply other threads:[~2024-03-13 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 14:40 [Tarantool-patches] [PATCH luajit v3 0/6] profilers: refactor parsers Maxim Kokryashkin via Tarantool-patches
2024-03-13 14:40 ` Maxim Kokryashkin via Tarantool-patches [this message]
2024-03-13 14:40 ` [Tarantool-patches] [PATCH luajit v3 2/6] build: fix tool components handling Maxim Kokryashkin via Tarantool-patches
2024-03-13 14:40 ` [Tarantool-patches] [PATCH luajit v3 3/6] memprof: refactor `heap_chunk` data structure Maxim Kokryashkin via Tarantool-patches
2024-03-13 14:40 ` [Tarantool-patches] [PATCH luajit v3 4/6] memprof: remove unused arguments Maxim Kokryashkin via Tarantool-patches
2024-03-13 14:40 ` [Tarantool-patches] [PATCH luajit v3 5/6] memprof: introduce the `--human-readable` option Maxim Kokryashkin via Tarantool-patches
2024-03-13 14:40 ` [Tarantool-patches] [PATCH luajit v3 6/6] profilers: introduce event reader module Maxim Kokryashkin via Tarantool-patches
2024-03-15 8:44 ` [Tarantool-patches] [PATCH luajit v3 0/6] profilers: refactor parsers Sergey Kaplun via Tarantool-patches
2024-03-20 15:08 ` Sergey Kaplun 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=fe7ac994b4082938d2edbda3051dadb857529a42.1710340671.git.m.kokryashkin@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=max.kokryashkin@gmail.com \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit v3 1/6] build: purge sysprof.collapse module' \
/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