From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: 71023@debbugs.gnu.org
Subject: [bug#71023] [PATCH 0/9] Update fzf to 0.52.1
Date: Tue, 21 May 2024 21:49:10 +0100 [thread overview]
Message-ID: <871q5uao1l.fsf@gmail.com> (raw)
In-Reply-To: <cover.1715964816.git.luishenriquegh2701@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
Hi,
Thank you for the patches.
From the first glance, some of the changes need to be grouped as single commit
- [PATCH 8/9] gnu: golang.scm: Update packages and go versions.
A general cement to all of them - is everything related just to bump fzf
to the latest version or it's a collection of not related patches?
I'm on the way to update valve to the latest version which is quite a
massive change in dependencies tree.
Also try to avoid adding any new packages to golang.scm.
--
Oleg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2024-05-21 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 0:32 [bug#71023] [PATCH 0/9] Update fzf to 0.52.1 Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 1/9] gnu: Add go-github-com-charlievieth-fastwalk Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 2/9] gnu: aerc: Update go version Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 3/9] gnu: vale: " Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 4/9] gnu: senpai: " Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 5/9] gnu: chezmoi: " Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 6/9] gnu: games.scm: Update go versions Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 7/9] gnu: golang-xyz.scm: " Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 8/9] gnu: golang.scm: Update packages and " Luis Higino
2024-05-18 1:11 ` [bug#71023] [PATCH 9/9] gnu: go-github-com-junegunn-fzf: Update to 0.52.1 Luis Higino
2024-05-21 20:49 ` Sharlatan Hellseher [this message]
2024-06-04 17:00 ` [bug#71023] [PATCH 0/9] Update fzf " Luis Henrique Gomes Higino
2024-06-10 10:14 ` [bug#71023] Groups Andreas Enge
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=871q5uao1l.fsf@gmail.com \
--to=sharlatanus@gmail.com \
--cc=71023@debbugs.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).