unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Brendan Tildesley <mail@brendan.scot>, 54337@debbugs.gnu.org
Subject: [bug#54337] [PATCH 1/2] gnu: Add boost-1.77/fixed.
Date: Fri, 11 Mar 2022 23:03:10 +0100	[thread overview]
Message-ID: <61782b44f00238c5fa213a84ca5f47db105dba3a.camel@telenet.be> (raw)
In-Reply-To: <20220311061925.11865-1-mail@brendan.scot>

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

Brendan Tildesley schreef op vr 11-03-2022 om 17:19 [+1100]:
> +(define-public boost-1.77/fixed

foo/fixed is conventionally used for graft-style security fixes, I
would prefer using a different variable name (unfortunately I'm not
feeling particularly inspired with names currently ...).

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-03-11 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  6:16 [bug#54337] [PATCHES 0/2] gnu: cryfs: Update to 0.11.2 Brendan Tildesley
2022-03-11  6:19 ` [bug#54337] [PATCH 1/2] gnu: Add boost-1.77/fixed Brendan Tildesley
2022-03-11  6:19   ` [bug#54337] [PATCH 2/2] gnu: cryfs: Update to 0.11.2 Brendan Tildesley
2022-03-11 22:03   ` Maxime Devos [this message]
2022-03-14  9:35 ` [bug#54337] [PATCH v2 1/3] gnu: crypto++: Update to 8.6.0 'Brendan Tildesley
2022-03-14  9:35   ` [bug#54337] [PATCH v2 2/3] gnu: Add boost-for-cryfs 'Brendan Tildesley
2022-03-15  8:14     ` Ludovic Courtès
2022-03-15 13:07       ` Brendan Tildesley
2022-03-15 16:35         ` Maxime Devos
2022-03-16  3:03       ` [bug#54337] [PATCH v3] gnu: Update crfys to 0.11.2 Brendan Tildesley
2022-03-16 10:40         ` Ludovic Courtès
2022-03-14  9:35   ` [bug#54337] [PATCH v2 3/3] gnu: cryfs: Update " 'Brendan Tildesley

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=61782b44f00238c5fa213a84ca5f47db105dba3a.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54337@debbugs.gnu.org \
    --cc=mail@brendan.scot \
    /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).