From: Lars-Dominik Braun <lars@6xq.net>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 52784-done@debbugs.gnu.org
Subject: bug#52784: [PATCH 4/5 v2] Add xmonad-next and ghc-xmonad-contrib-next.
Date: Mon, 17 Jan 2022 20:32:13 +0100 [thread overview]
Message-ID: <YeXEPXqz7NweZV8J@noor.fritz.box> (raw)
In-Reply-To: <fQ2LTSbCDOdUr3GFsNHK2ZhqUeXEGie3ebWvHS3d8iSIKEEX6GStloi-3xLg2eQhOdcCRvBjtUQNx8tcRlaH2HYti16MS6dDaRhKSPwxQns=@protonmail.com>
Hi John,
> Yes, that makes more sense, let's go with that.
I merged your patches as 5387a9c00ef2f972c32ab4430a3f1879131b1652 and
following. Thank you!
> Ah, good to know. (I've been using polybar but have a huge stack of packages to add taffybar. I've been putting off submitting it because it is a lot of packages that I need to figure where each goes, but I'll get to it. If you were interested in trying out taffybar, let me know and I can make the WIP patches available for testing.)
Sure, I can try out taffybar.
Cheers,
Lars
prev parent reply other threads:[~2022-01-17 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 19:22 [bug#52784] [PATCH 0/5] Update XMonad (and add new dependencies) John Kehayias via Guix-patches via
2021-12-24 19:28 ` [bug#52784] [PATCH 1/5] " John Kehayias via Guix-patches via
2021-12-24 19:29 ` [bug#52784] [PATCH 2/5] " John Kehayias via Guix-patches via
2021-12-24 19:29 ` [bug#52784] [PATCH 3/5] " John Kehayias via Guix-patches via
2021-12-24 19:29 ` [bug#52784] [PATCH 4/5] " John Kehayias via Guix-patches via
2021-12-24 19:30 ` [bug#52784] [PATCH 5/5] " John Kehayias via Guix-patches via
2021-12-28 10:24 ` [bug#52784] [PATCH 0/5] " Lars-Dominik Braun
2021-12-28 19:15 ` John Kehayias via Guix-patches via
2022-01-10 1:54 ` [bug#52784] [PATCH 4/5 v2] Add xmonad-next and ghc-xmonad-contrib-next John Kehayias via Guix-patches via
2022-01-15 10:38 ` Lars-Dominik Braun
2022-01-15 18:49 ` John Kehayias via Guix-patches via
2022-01-17 19:32 ` Lars-Dominik Braun [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=YeXEPXqz7NweZV8J@noor.fritz.box \
--to=lars@6xq.net \
--cc=52784-done@debbugs.gnu.org \
--cc=john.kehayias@protonmail.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 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).