Done.
On 21 May 2015 at 12:25, Ludovic Courtès wrote:
> Perhaps you could cherry-pick these changes in ‘core-updates’ and then
> rebase ‘wip-hurd’ on top of it? WDYT?
That's sound like a good idea. Will push those two to core-updates,
rebase wip-hurd on top of core-updates and push the new wip-hurd.
How should we manage branches?
There are improvements like these Bison and Flex changes that could go
to ‘core-updates’, which would be beneficial to everyone in the long
term.
Perhaps you could cherry-pick these changes in ‘core-updates’ and then
rebase ‘wip-hurd’ on top of it? WDYT?
Ludo’.
Pushed to wip-hurd.
Manolis
Manolis Ragkousis skribis:
> From 341be976921664ca8c2c071fcbf0e0c2df6224a5 Mon Sep 17 00:00:00 2001
> From: Manolis Ragkousis
> Date: Tue, 12 May 2015 20:42:38 +0300
> Subject: [PATCH 05/10] gnu: bison: Add m4 as a native input.
>
> * gnu/packages/bison (bison): Add m4 as a
From 341be976921664ca8c2c071fcbf0e0c2df6224a5 Mon Sep 17 00:00:00 2001
From: Manolis Ragkousis
Date: Tue, 12 May 2015 20:42:38 +0300
Subject: [PATCH 05/10] gnu: bison: Add m4 as a native input.
* gnu/packages/bison (bison): Add m4 as a native input.
---
gnu/packages/bison.scm | 4 +++-
1 file
