all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 61560@debbugs.gnu.org
Subject: [bug#61560] [Guix Data Service] Comparing package derivations: Fix inconsistent verbage.
Date: Thu, 16 Feb 2023 17:26:45 -0500	[thread overview]
Message-ID: <b567b089d484aa3eea08063f16bb1dca193f84f7.1676586405.git.leo@famulari.name> (raw)

Harmonize "Build change" options between the selection menu and the documentation

I don't have a preference about which phrase is chosen. Please use your
judgement in fixing this to ensure consistency throughout the user interface.

* guix-data-service/web/compare/html.scm (compare/package-derivations): Replace
"Still broken" with "Still failing" in the "Build change" help text.
---
 guix-data-service/web/compare/html.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guix-data-service/web/compare/html.scm b/guix-data-service/web/compare/html.scm
index 58fb514..44acb81 100644
--- a/guix-data-service/web/compare/html.scm
+++ b/guix-data-service/web/compare/html.scm
@@ -797,7 +797,7 @@ derivation")
                            (dd
                             "At least one successful build for both the base
 and target derivations")
-                           (dt "Still broken")
+                           (dt "Still failing")
                            (dd
                             "No successful builds and at least one failed builds for both the base and target derivations")
                            (dt "Unknown")
-- 
2.39.1





             reply	other threads:[~2023-02-16 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 22:26 Leo Famulari [this message]
2023-02-17 17:11 ` bug#61560: [Guix Data Service] Comparing package derivations: Fix inconsistent verbage Christopher Baines

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b567b089d484aa3eea08063f16bb1dca193f84f7.1676586405.git.leo@famulari.name \
    --to=leo@famulari.name \
    --cc=61560@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.