From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Nicolas Graves" <ngraves@ngraves.fr>,
70400@debbugs.gnu.org, jpieper@mailbox.org
Subject: [bug#70400] [PATCH] Update python-lsp-server
Date: Tue, 18 Jun 2024 08:49:33 +0000 [thread overview]
Message-ID: <c7d9d98fdb46e86f8032537340b019ebc16bcefb@dismail.de> (raw)
In-Reply-To: <87sezmsf33.fsf@mailbox.org>
Hi,
Should we close this ticket?
This update is already on the python-team branch authored by rekado.
all best,
jgart
prev parent reply other threads:[~2024-06-18 9:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 17:34 [bug#70400] [PATCH] Update python-lsp-server Jonathan Pieper via Guix-patches via
2024-04-15 17:45 ` [bug#70400] [PATCH 1/7] gnu: Add python-docstring-to-markdown Jonathan Pieper via Guix-patches via
2024-04-15 17:45 ` [bug#70400] [PATCH 2/7] gnu: Add python-pytoolconfig Jonathan Pieper via Guix-patches via
2024-06-15 22:45 ` Nicolas Graves via Guix-patches via
2024-04-15 17:45 ` [bug#70400] [PATCH 3/7] gnu: python-lsp-jsonrpc: Update to 1.1.2 Jonathan Pieper via Guix-patches via
2024-06-15 22:53 ` Nicolas Graves via Guix-patches via
2024-04-15 17:45 ` [bug#70400] [PATCH 4/7] gnu: python-snowballstemmer: Update to 2.2.0 Jonathan Pieper via Guix-patches via
2024-04-15 17:45 ` [bug#70400] [PATCH 5/7] gnu: python-pydocstyle: Update to 6.3.0 Jonathan Pieper via Guix-patches via
2024-04-15 17:45 ` [bug#70400] [PATCH 6/7] gnu: python-rope: Update to 1.13.0 Jonathan Pieper via Guix-patches via
2024-04-15 17:45 ` [bug#70400] [PATCH 7/7] gnu: python-lsp-server: Update to 1.11.0 Jonathan Pieper via Guix-patches via
2024-06-15 23:10 ` Nicolas Graves via Guix-patches via
2024-06-15 22:29 ` [bug#70400] [PATCH 1/7] gnu: Add python-docstring-to-markdown Nicolas Graves via Guix-patches via
2024-06-15 22:23 ` [bug#70400] [PATCH] Update python-lsp-server Nicolas Graves via Guix-patches via
2024-06-18 8:49 ` jgart via Guix-patches via [this message]
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=c7d9d98fdb46e86f8032537340b019ebc16bcefb@dismail.de \
--to=guix-patches@gnu.org \
--cc=70400@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=jpieper@mailbox.org \
--cc=ngraves@ngraves.fr \
/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.