From: Marius Bakke <mbakke@fastmail.com>
To: 28330@debbugs.gnu.org
Subject: [bug#28330] [PATCH 0/2] Boost 1.65.0.
Date: Sat, 2 Sep 2017 15:05:50 +0200 [thread overview]
Message-ID: <20170902130550.28061-1-mbakke@fastmail.com> (raw)
Boost issued a couple of post-release patches for 1.65.0. See
<http://www.boost.org/users/history/version_1_65_0.html>. Should we
include them? I've done that here (but skipped the Windows ones..).
`lint` complained that the patches did not have good file names, even
when explicitly set, so I extended it to check origin-file-names.
Feedback wanted!
Note: MySQL (at least) fails to build against 1.65.0, so we may need
to keep 1.64.0 around.
Marius Bakke (2):
lint: Check file names of origin patches.
gnu: boost: Update to 1.65.0.
gnu/packages/boost.scm | 26 ++++++++++++++++++++++++--
guix/scripts/lint.scm | 8 +++++++-
2 files changed, 31 insertions(+), 3 deletions(-)
--
2.14.1
next reply other threads:[~2017-09-02 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 13:05 Marius Bakke [this message]
2017-09-02 13:09 ` [bug#28330] [PATCH 1/2] lint: Check file names of origin patches Marius Bakke
2017-09-02 13:09 ` [bug#28330] [PATCH staging 2/2] gnu: boost: Update to 1.65.0 Marius Bakke
2017-09-05 13:12 ` Ludovic Courtès
2017-09-05 13:11 ` [bug#28330] [PATCH 1/2] lint: Check file names of origin patches Ludovic Courtès
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=20170902130550.28061-1-mbakke@fastmail.com \
--to=mbakke@fastmail.com \
--cc=28330@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 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).