From: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Fixing Zabbix db-secret-file documentation.
Date: Sun, 08 Nov 2020 01:48:10 +0100 [thread overview]
Message-ID: <87h7q07jxx.fsf@gmail.com> (raw)
In-Reply-To: <87wnyx72qz.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sat, 07 Nov 2020 13:47:16 +0100")
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Hi!
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> I've changed it to front-end just for consistency... for now ;-) and
> pushed to master as 83dee0e5b29dee75cffd5aa2a7748697eb73b036. If
> nobody objects I'll cherry-pick it to version-1.2.0 before the
> release. That'll be the on-line manual for some time to come.
I have to raise my hand here, as TP.org hasn't updated their page yet,
or at least I haven't received the email yet, but the tarball was
already sent. Perhaps we're lucky and the first mail may end in
/dev/null with no fuss if we send the update soon.... Julien, WDYT?
Just for the record, I'm glad to translate that change or whatever comes
next, but it makes me a bit sad when that effort is reduced to a number,
because that "number" means making accessible the documentation to
people who don't speak English. I understand what you meant, and I
agree about the change too; I just wanted to clarify that it isn't a
matter of boosting stats but working together.
Happy hacking!
Miguel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
next prev parent reply other threads:[~2020-11-08 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 13:29 Fixing Zabbix db-secret-file documentation Tobias Geerinckx-Rice
2020-11-07 12:19 ` Oleg Pykhalov
2020-11-07 12:47 ` Tobias Geerinckx-Rice
2020-11-08 0:48 ` Miguel Ángel Arruga Vivas [this message]
2020-11-08 23:27 ` Tobias Geerinckx-Rice
2020-11-09 11:54 ` Miguel Ángel Arruga Vivas
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=87h7q07jxx.fsf@gmail.com \
--to=rosen644835@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).