From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 61195-done@debbugs.gnu.org
Subject: bug#61195: termite failed to build, need switch to a maintained fork
Date: Tue, 01 Aug 2023 19:55:17 +0800 [thread overview]
Message-ID: <874jljyo2i.fsf@envs.net> (raw)
In-Reply-To: <87357rywjk.fsf@envs.net> ("宋文武"'s message of "Tue, 31 Jan 2023 15:48:15 +0800")
> New fork: https://github.com/aperezdc/termite
> Maybe also remove vte-ng.
Done in commit 1b8c5480f64a57f46e39822136d279fa0b1270cd and
34b56974dfe720e5e30f04409ac216747d7e3f5c.
prev parent reply other threads:[~2023-08-01 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 7:48 bug#61195: termite failed to build, need switch to a maintained fork 宋文武 via Bug reports for GNU Guix
2023-08-01 11:55 ` 宋文武 via Bug reports for GNU Guix [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
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=874jljyo2i.fsf@envs.net \
--to=bug-guix@gnu.org \
--cc=61195-done@debbugs.gnu.org \
--cc=iyzsong@envs.net \
/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).