From: Blake Shaw via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 52372@debbugs.gnu.org, 52372-done@debbugs.gnu.org
Subject: bug#52372: gash-utils & fzf conflict
Date: Thu, 09 Dec 2021 12:29:14 +0700 [thread overview]
Message-ID: <87ee6mmjmd.fsf@nonconstructivism.com> (raw)
In-Reply-To: <87k0gfuhke.fsf@nckx> (Tobias Geerinckx-Rice's message of "Wed, 08 Dec 2021 18:14:12 +0100")
Tobias Geerinckx-Rice <me@tobias.gr> writes:
got it, thanks!
--
“In girum imus nocte et consumimur igni”
next prev parent reply other threads:[~2021-12-09 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 11:23 bug#52372: gash-utils & fzf conflict Blake Shaw via Bug reports for GNU Guix
2021-12-08 17:14 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-12-09 5:29 ` Blake Shaw via Bug reports for GNU Guix [this message]
2021-12-11 16:12 ` Timothy Sample
2021-12-08 17:30 ` Maxime Devos
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=87ee6mmjmd.fsf@nonconstructivism.com \
--to=bug-guix@gnu.org \
--cc=52372-done@debbugs.gnu.org \
--cc=52372@debbugs.gnu.org \
--cc=blake@nonconstructivism.com \
--cc=me@tobias.gr \
/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).