From: Adriel Dumas--Jondeau via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 67038@debbugs.gnu.org
Cc: "Christopher Baines" <guix@cbaines.net>,
"Josselin Poiret" <dev@jpoiret.xyz>,
"Ludovic Courtès" <ludo@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>,
"Ricardo Wurmus" <rekado@elephly.net>,
"Simon Tournier" <zimon.toutoune@gmail.com>,
"Tobias Geerinckx-Rice" <me@tobias.gr>
Subject: bug#67038: [PATCH] guix: status: Fix ellipsis inconsistencies.
Date: Sun, 19 Nov 2023 17:55:40 +0100 [thread overview]
Message-ID: <44b644651d0cc182b89b8bbb7198f958db7c6666.1700412533.git.leirda@disroot.org> (raw)
In-Reply-To: <87wmuq9dfy.fsf@elephly.net>
Fixes <https://issues.guix.gnu.org/67038>.
Reported by Ricardo Wurmus.
* guix/status.scm (print-build-event): Fix ellipsis inconsistencies.
---
guix/status.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
We just made this patch after Capitole du Libre at Toulouse as an example for
my first patch \o/
diff --git a/guix/status.scm b/guix/status.scm
index fd89ba9dd3..0ed6d3318a 100644
--- a/guix/status.scm
+++ b/guix/status.scm
@@ -494,8 +494,8 @@ (define* (print-build-event event old-status status
(let ((count (match (assq-ref properties 'graft)
(#f 0)
(lst (or (assq-ref lst 'count) 0)))))
- (format port (info (N_ "applying ~a graft for ~a ..."
- "applying ~a grafts for ~a ..."
+ (format port (info (N_ "applying ~a graft for ~a..."
+ "applying ~a grafts for ~a..."
count))
count
(string-drop-right (store-path-package-name drv)
base-commit: 761810d32a0550912b5bb36a0c9f60141bcb7d20
--
2.41.0
prev parent reply other threads:[~2023-11-22 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 9:12 bug#67038: Inconsistent use of space before ellipsis Ricardo Wurmus
2023-11-16 9:43 ` Simon Tournier
2023-11-16 14:09 ` pelzflorian (Florian Pelz)
2023-11-17 15:47 ` Ludovic Courtès
2023-11-19 16:55 ` Adriel Dumas--Jondeau 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=44b644651d0cc182b89b8bbb7198f958db7c6666.1700412533.git.leirda@disroot.org \
--to=bug-guix@gnu.org \
--cc=67038@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=leirda@disroot.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.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).