From: paul via Guix-patches via <guix-patches@gnu.org>
To: jgart <jgart@dismail.de>, 66886@debbugs.gnu.org
Cc: Munyoki Kilyungi <me@bonfacemunyoki.com>,
Lars-Dominik Braun <lars@6xq.net>, Marius Bakke <marius@gnu.org>
Subject: [bug#66886] [PATCH 5/5] gnu: python-textual: Update to 0.41.0.
Date: Fri, 17 Nov 2023 00:55:04 +0100 [thread overview]
Message-ID: <5dc0da91-abd5-839c-88fa-9dbfd3cd3099@autistici.org> (raw)
In-Reply-To: <3ed2e84b6984b8a0ccfa12982acf40c2@dismail.de>
Hi jgart,
On 11/2/23 01:14, jgart wrote:
> Hi,
>
> Thanks for sending this patch set. I'll try to review this week(end).
>
> all best,
>
> jgart
I'm sending an updated patchset rebased on current master.
Thank you for your time,
giacomo
next prev parent reply other threads:[~2023-11-16 23:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 16:58 [bug#66886] Update python-textual to 0.41 paul via Guix-patches via
2023-11-01 17:01 ` [bug#66886] [PATCH 1/5] gnu: Add python-pygments-2.16 Giacomo Leidi via Guix-patches via
2023-11-01 17:01 ` [bug#66886] [PATCH 2/5] gnu: python-markdown-it-py: Update to 3.0.0 Giacomo Leidi via Guix-patches via
2023-11-01 17:01 ` [bug#66886] [PATCH 3/5] gnu: python-rich: Update to 13.6.0 Giacomo Leidi via Guix-patches via
2023-11-01 17:01 ` [bug#66886] [PATCH 4/5] gnu: python-mdit-py-plugins: Update to 0.4.0 Giacomo Leidi via Guix-patches via
2023-11-01 17:01 ` [bug#66886] [PATCH 5/5] gnu: python-textual: Update to 0.41.0 Giacomo Leidi via Guix-patches via
2023-11-02 0:14 ` jgart via Guix-patches via
2023-11-16 23:55 ` paul via Guix-patches via [this message]
2023-11-18 2:44 ` jgart via Guix-patches via
2023-12-03 15:21 ` paul via Guix-patches via
2023-12-29 22:07 ` paul via Guix-patches via
2024-01-14 23:54 ` paul via Guix-patches via
2024-02-27 18:42 ` paul via Guix-patches via
2024-02-27 18:42 ` bug#66886: " paul via Guix-patches via
2023-11-16 23:54 ` [bug#66886] [PATCH v2 1/5] gnu: Add python-pygments-2.16 Giacomo Leidi via Guix-patches via
2023-11-16 23:54 ` [bug#66886] [PATCH v2 2/5] gnu: python-markdown-it-py: Update to 3.0.0 Giacomo Leidi via Guix-patches via
2023-11-16 23:54 ` [bug#66886] [PATCH v2 3/5] gnu: python-rich: Update to 13.7.0 Giacomo Leidi via Guix-patches via
2023-11-16 23:54 ` [bug#66886] [PATCH v2 4/5] gnu: python-mdit-py-plugins: Update to 0.4.0 Giacomo Leidi via Guix-patches via
2023-11-16 23:54 ` [bug#66886] [PATCH v2 5/5] gnu: python-textual: Update to 0.41.0 Giacomo Leidi via Guix-patches via
2023-12-03 15:22 ` [bug#66886] [PATCH v3 1/6] gnu: Add python-pygments-2.16 Giacomo Leidi via Guix-patches via
2023-12-03 15:22 ` [bug#66886] [PATCH v3 2/6] gnu: python-markdown-it-py: Update to 3.0.0 Giacomo Leidi via Guix-patches via
2023-12-03 15:22 ` [bug#66886] [PATCH v3 3/6] gnu: python-rich: Update to 13.7.0 Giacomo Leidi via Guix-patches via
2023-12-03 15:22 ` [bug#66886] [PATCH v3 4/6] gnu: python-jupytext: Update to 1.15.2 Giacomo Leidi via Guix-patches via
2023-12-03 15:22 ` [bug#66886] [PATCH v3 5/6] gnu: python-mdit-py-plugins: Update to 0.4.0 Giacomo Leidi via Guix-patches via
2023-12-03 15:22 ` [bug#66886] [PATCH v3 6/6] gnu: python-textual: Update to 0.41.0 Giacomo Leidi via Guix-patches via
2024-01-14 23:59 ` [bug#66886] [PATCH v4 1/6] gnu: Add python-pygments-2.16 Giacomo Leidi via Guix-patches via
2024-01-14 23:59 ` [bug#66886] [PATCH v4 2/6] gnu: python-markdown-it-py: Update to 3.0.0 Giacomo Leidi via Guix-patches via
2024-01-14 23:59 ` [bug#66886] [PATCH v4 3/6] gnu: python-rich: Update to 13.7.0 Giacomo Leidi via Guix-patches via
2024-01-14 23:59 ` [bug#66886] [PATCH v4 4/6] gnu: python-jupytext: Update to 1.15.2 Giacomo Leidi via Guix-patches via
2024-01-14 23:59 ` [bug#66886] [PATCH v4 5/6] gnu: python-mdit-py-plugins: Update to 0.4.0 Giacomo Leidi via Guix-patches via
2024-01-14 23:59 ` [bug#66886] [PATCH v4 6/6] gnu: python-textual: Update to 0.47.1 Giacomo Leidi via Guix-patches via
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=5dc0da91-abd5-839c-88fa-9dbfd3cd3099@autistici.org \
--to=guix-patches@gnu.org \
--cc=66886@debbugs.gnu.org \
--cc=goodoldpaul@autistici.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.