unofficial mirror of guix-devel@gnu.org 
 help / color / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: MPFR and MPC
Date: Tue, 28 Jul 2020 11:37:47 +0200
Message-ID: <20200728093747.GA5975@LionPure> (raw)
In-Reply-To: <20200723133621.GA25143@jurong>

Hi,

On +2020-07-23 15:36:21 +0200, Andreas Enge wrote:
> Hello,
> 
> mpfr just had a new release 4.1.0:
>    https://ftp.gnu.org/pub/gnu/mpfr/
> and I am planning to make one for mpc as well.
> 
> Should I follow some procedure for an update in Guix, or could I just push
> two commits to core-updates?
> 
> Andreas
> 
> 
It would seem easy to forget that all readers may not know what MPFR and MPC
(and other acronyms) mean, yet be curious enough to want to look them up ;-)

To help such people, I think it would be great if "info guix acronyms"
searched for and found a glossary section (e.g. 14.9 Acronyms ?) with an
easy index that would also mostly succeed with e.g., "info guix|grep -iwC5 mpfr"
(which BTW does find something to go on right now, but not a definition)


From info guix:
--8<---------------cut here---------------start------------->8---
14.4.4 Synopses and Descriptions
--------------------------------
[...]
   Descriptions should take between five and ten lines.  Use full
sentences, and avoid using acronyms without first introducing them.
--8<---------------cut here---------------end--------------->8---

ISTM using this advice would be good for posting to the mailing list
when meanings are not obvious from thread context.

Otherwise acronyms come across a little like identity challenges,
saying "if you don't know what that means, you don't belong in this meeting."

(well, that might be true sometimes for meetings of specialists with urgent work to do,
but not for inclusive public mailing lists :)

-- 
Regards,
Bengt Richter


  parent reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 13:36 Andreas Enge
2020-07-27 10:58 ` Ludovic Courtès
2020-07-28 12:57   ` Andreas Enge
2020-07-28  9:37 ` Bengt Richter [this message]
2020-07-28 10:00   ` zimoun

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=20200728093747.GA5975@LionPure \
    --to=bokr@bokr.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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

unofficial mirror of guix-devel@gnu.org 

Archives are clonable:
	git clone --mirror https://yhetil.org/guix-devel/0 guix-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-devel guix-devel/ https://yhetil.org/guix-devel \
		guix-devel@gnu.org
	public-inbox-index guix-devel

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.devel
	nntp://news.gmane.io/gmane.comp.gnu.guix.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git