From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Igor Munkin <imun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 luajit 0/3] Introduce gdb extension for LuaJIT
Date: Thu, 27 Feb 2020 01:45:09 +0300 [thread overview]
Message-ID: <20200226224509.wunwgszrilnnmykf@tkn_work_nb> (raw)
In-Reply-To: <cover.1580917791.git.imun@tarantool.org>
Are not it worth to squash those commits? Now the series looks as
'feature + fixup + fixup' and since we don't pushed it yet to a
long-term branch is looks okay to squash fixups into the first commit.
It is up to you, I just asked.
WBR, Alexander Turenko.
next prev parent reply other threads:[~2020-02-26 22:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 16:22 Igor Munkin
2020-02-05 16:22 ` [Tarantool-patches] [PATCH v2 luajit 1/3] gdb: introduce luajit-gdb extension Igor Munkin
2020-02-13 13:24 ` Igor Munkin
2020-02-05 16:22 ` [Tarantool-patches] [PATCH v2 luajit 2/3] gdb: adjust the extension to be used with Python 2 Igor Munkin
2020-02-05 16:22 ` [Tarantool-patches] [PATCH v2 luajit 3/3] gdb: enhance the extension loading Igor Munkin
2020-02-13 11:48 ` Igor Munkin
2020-02-13 12:24 ` Igor Munkin
2020-02-26 22:41 ` [Tarantool-patches] [PATCH v2 luajit 0/3] Introduce gdb extension for LuaJIT Alexander Turenko
2020-02-28 10:46 ` Igor Munkin
2020-03-02 16:00 ` Igor Munkin
2020-03-03 14:16 ` Sergey Ostanevich
2020-02-26 22:45 ` Alexander Turenko [this message]
2020-02-27 10:48 ` Igor Munkin
2020-02-27 11:35 ` Alexander Turenko
2020-03-03 16:17 ` Igor Munkin
2020-03-03 22:39 ` Alexander Turenko
2020-03-17 22:46 ` Igor Munkin
2020-02-26 23:04 ` Alexander Turenko
2020-02-27 10:13 ` Igor Munkin
2020-02-26 23:10 ` Alexander Turenko
2020-02-27 10:37 ` Igor Munkin
2020-03-05 7:44 ` Kirill Yukhin
2020-03-05 9:22 ` Igor Munkin
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=20200226224509.wunwgszrilnnmykf@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=imun@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 luajit 0/3] Introduce gdb extension for LuaJIT' \
/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