[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] gnu: icu4c: Upgrade to 52.1
|
From: |
Mark H Weaver |
|
Subject: |
Re: [PATCH] gnu: icu4c: Upgrade to 52.1 |
|
Date: |
Mon, 17 Feb 2014 14:15:43 -0500 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
address@hidden (Ludovic Courtès) writes:
> Mark H Weaver <address@hidden> skribis:
>
>> From bb44edacf768c8308f7d64ad16a10ca9c924469d Mon Sep 17 00:00:00 2001
>> From: Mark H Weaver <address@hidden>
>> Date: Sun, 16 Feb 2014 16:38:00 -0500
>> Subject: [PATCH] gnu: icu4c: Upgrade to 52.1.
>>
>> * gnu/packages/icu4c.scm (icu4c): Upgrade to 52.1.
>
> OK to push, but rather on ‘core-updates’ to limit rebuilds, as discussed
> yesterday.
FWIW, the 'patchelf' fix will trigger a rebuild of icu4c anyway. So it
would cause no additional work if these two commits were simultaneously
pushed to 'master'.
Alternatively, they could both be pushed to core-updates only. I need
the 'patchelf' fix now, but I can keep that on my local branch off
master, I suppose.
What do you think?
Mark