One question. Does this backporting work happen a lot? If so, is the stable
branch really helping things if there is a lot of repeated work ?
Aloha,
RK.
On Thu, Jan 8, 2015 at 11:59 PM, Shea Levy s...@shealevy.com wrote:
Ah, actually I see Peter already brought haskell-ng into master via the
No, if it happens at all it’s usually just a cherry-pick (which is very easy).
Anyway, the point of the stable branch is to provide a reliable experience to
end users, not necessarily to make things easier on developers. And, with the
exception of urgent security fixes, changes are only
Hi all,
I’d like to make a case for backporting Peter’s haskell-ng work to 14.12 once
it’s merged into master. If I understand correctly, then if a haskell package’s
version (and the versions of its dependency closure) stay the same, the
haskell-ng branch will result in what is effectively the
Ah, actually I see Peter already brought haskell-ng into master via the
haskellngPackages attribute. So I’ll just backport that, as it won’t touch any
existing haskellPackages stuff. Never mind!
On Jan 8, 2015, at 1:07 PM, Shea Levy s...@shealevy.com wrote:
Hi all,
I’d like to make a
