From: Csepp <raingloom@riseup.net>
To: guix-devel <guix-devel@gnu.org>
Subject: kak-lsp upgrade
Date: Fri, 02 Dec 2022 02:01:07 +0100 [thread overview]
Message-ID: <87zgc67h10.fsf@riseup.net> (raw)
Hi!
I upgraded the kak-lsp package through some blood and sweat, but I
really don't have the patience to also sort the commits out, I have my
thesis project and exams to work on.
If anyone wants to take a stab at it or make etc/commiter.scm more
useful in situations like this, I'd be super thankful. Specifically it
really shouldn't decide what should go into the commit, it should just
write the commit message based on the staged changes.
https://git.sr.ht/~raingloom/guix-source/log/raingloom/kak-lsp
Rust packaging is a nightmare btw. When will antioxidant hit the master
branch?
reply other threads:[~2022-12-02 1:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgc67h10.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).