From mboxrd@z Thu Jan  1 00:00:00 1970
From: Danny Milosavljevic <dannym@scratchpost.org>
Subject: Re: [PATCH] gnu: boost: Update to 1.63.0.
Date: Tue, 17 Jan 2017 21:36:36 +0100
Message-ID: <20170117213625.547030df@scratchpost.org>
References: <20170113232854.31807-1-dannym@scratchpost.org>
	<87ziirxgno.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44184)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dannym@scratchpost.org>) id 1cTaUo-0005Ll-W8
	for guix-devel@gnu.org; Tue, 17 Jan 2017 15:36:47 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dannym@scratchpost.org>) id 1cTaUk-0008SO-V0
	for guix-devel@gnu.org; Tue, 17 Jan 2017 15:36:46 -0500
In-Reply-To: <87ziirxgno.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?ISO-8859-1?Q?Court=E8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

Hi Ludo,

On Mon, 16 Jan 2017 14:45:15 +0100
ludo@gnu.org (Ludovic Court=C3=A8s) wrote:

> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>=20
> > * gnu/packages/boost.scm (boost): Update to 1.63.0. =20
>=20
> I think this could go in a new =E2=80=98staging=E2=80=99 branch, unless w=
e expect
> breakage, in which case a =E2=80=98boost-updates=E2=80=99 branch may be m=
ore
> appropriate.

Okay. I don't think a minor version update causes breakage - but let's see.

I've pushed it to 'staging', commit 4c9c8a294ea64fcb969da84e6fe207780ebdb38=
7.