From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Josefsson via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: Simon Josefsson <simon@josefsson.org>
Subject: Re: advanced?
Date: Wed, 04 Jan 2023 11:54:56 +0100 [thread overview]
Message-ID: <878rii603j.fsf@gnu.org> (raw)
In-Reply-To: <875yf1qtfq.fsf@latte> (Simon Josefsson via's message of "Sat, 26 Nov 2022 22:47:37 +0100")
Hi Simon and all,
Simon Josefsson via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> skribis:
> From aac8f6d1fb382b9f9120b7cd51dc80e8ef07cc03 Mon Sep 17 00:00:00 2001
> From: Simon Josefsson <simon@josefsson.org>
> Date: Sat, 26 Nov 2022 22:35:15 +0100
> Subject: [PATCH] website: Reduce use of 'advanced' term.
>
> ---
> website/apps/base/templates/about.scm | 4 ++--
> website/apps/base/templates/home.scm | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
It’s been a month and it looks like there wasn’t any opposition to this
change, so I went ahead and pushed it.
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-01-04 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 21:47 advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-27 8:51 ` advanced? Liliana Marie Prikler
2022-11-27 12:39 ` advanced? zimoun
2022-11-27 17:22 ` advanced? Ryan Prior
2022-11-27 18:35 ` advanced? Vagrant Cascadian
2022-11-28 11:18 ` advanced? Ludovic Courtès
2022-11-28 14:44 ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 18:36 ` advanced? zimoun
2023-01-04 11:00 ` advanced? Ludovic Courtès
2023-01-09 12:02 ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 15:35 ` advanced? Denis 'GNUtoo' Carikli
2023-01-04 10:54 ` Ludovic Courtès [this message]
2023-01-09 11:12 ` advanced? Ludovic Courtès
2023-01-09 11:37 ` advanced? Julien Lepiller
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=878rii603j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=simon@josefsson.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).