-maintainer for ‘happy’ who could make releases more frequently
(I understand the current maintainers probably don’t have the time to do it).
b) Use a development snapshot of ‘happy’ in GHC
Maybe we need to do both, but one reason I’d like to see (b) in particular
happen is that I can imagine
intainers probably don’t have the time to do it).
> b) Use a development snapshot of ‘happy’ in GHC
>
> Maybe we need to do both, but one reason I’d like to see (b) in particular
> happen is that I can imagine introducing more features to ‘happy’ for use in
> GHC, and it’d be
hub.com/simonmar/happy/issues/168
>
> I see two solutions here:
>
> a) Find a co-maintainer for ‘happy’ who could make releases more
> frequently (I understand the current maintainers probably don’t have
> the time to do it).
> b) Use a development snapshot of ‘happy’ in G
Find a co-maintainer for ‘happy’ who could make releases more
frequently (I understand the current maintainers probably don’t have
the time to do it).
b) Use a development snapshot of ‘happy’ in GHC
Maybe we need to do both, but one reason I’d like to see (b) in
particular happen is
://github.com/simonmar/happy/issues/168
I see two solutions here:
a) Find a co-maintainer for ‘happy’ who could make releases more frequently
(I understand the current maintainers probably don’t have the time to do it).
b) Use a development snapshot of ‘happy’ in GHC
Maybe we need to do both, but one
Ben Gamari writes:
> Vladislav Zavialov writes:
>
...
> It will be a tad more involved than this. We will need to teach the
> build systems to build Happy, use the configure executable, and update
My apologies. The above should have read:
> use the *produced* executable
signature.asc
nmar/happy/issues/168
>
> I see two solutions here:
>
> a) Find a co-maintainer for ‘happy’ who could make releases more
> frequently (I understand the current maintainers probably don’t have
> the time to do it).
> b) Use a development snapshot of ‘happy’ in G
/issues/164
2. Ben asked for a release a month ago:
https://github.com/simonmar/happy/issues/168
I see two solutions here:
a) Find a co-maintainer for ‘happy’ who could make releases more frequently
(I understand the current maintainers probably don’t have the time to do it).
b) Use a deve
appy/issues/168
>
> I see two solutions here:
>
> a) Find a co-maintainer for ‘happy’ who could make releases more frequently
> (I understand the current maintainers probably don’t have the time to do it).
> b) Use a development snapshot of ‘happy’ in GHC
>
> Maybe we n
make releases more frequently
(I understand the current maintainers probably don’t have the time to do it).
b) Use a development snapshot of ‘happy’ in GHC
Maybe we need to do both, but one reason I’d like to see (b) in particular
happen is that I can imagine introducing more features to ‘happy
Hello all,
I recently posted a bug report about cabal that's exposed by its interaction
with GHC HEAD, and one of the cabal devs reasonably asked about a snapshot of
HEAD somewhere. The link from http://www.haskell.org/ghc/download leads to an
empty directory. Is there another place I can
11 matches
Mail list logo
