Re: Cannot unsubscribe

2017-12-13 Thread cheater00 cheater00
Got it. Got filed under "promotions". On Thu, Dec 14, 2017 at 1:42 AM, cheater00 cheater00 wrote: > I went to http://mail.haskell.org/cgi-bin/mailman/options/ghc-devs > logged in and clicked on "unsubscribe" and no unsubscription email > shows up. What do i do to

Cannot unsubscribe

2017-12-13 Thread cheater00 cheater00
I went to http://mail.haskell.org/cgi-bin/mailman/options/ghc-devs logged in and clicked on "unsubscribe" and no unsubscription email shows up. What do i do to unsubscribe? Thanks ___ ghc-devs mailing list ghc-devs@haskell.org

Re: Long standing annoying issue in ghci

2017-12-13 Thread cheater00 cheater00
I went ahead and did this for you. On Tue, Dec 12, 2017 at 8:44 PM, cheater00 cheater00 wrote: > Yes, it is worth doing it, because until Haskeline has been fixed and > integrated into ghci, the issue persists and needs to remain filed. > > > On Fri, 8 Dec 2017 18:25

Re: Fwd: Release policies

2017-12-13 Thread Gershom B
On Wed, Dec 13, 2017 at 7:06 PM, Boespflug, Mathieu wrote: > > But crucially, what *is* the policy around Cabal versions? This > comment, https://ghc.haskell.org/trac/ghc/ticket/14558#comment:23 > claims "if Stack doesn't support the version of Cabal that ships with > a certain

Re: Fwd: Release policies

2017-12-13 Thread Boespflug, Mathieu
Hi Gerhom, On 14 December 2017 at 00:19, Gershom B wrote: > > Mathieu: > > I think the points about better tooling for documenting the correct > claims in the release process are well taken. Updating the release > notes manually leaves way too much room for error. > >

Re: Fwd: Release policies

2017-12-13 Thread Gershom B
. >> >> This is just a proposal. The narrow questions are these: >> >>- Would this be sufficient to deal with the concerns raised in #14558? >>- Is it necessary, ow would anything simpler be sufficient? >>- What costs would the policy impose on GHC dev

Fwd: Release policies

2017-12-13 Thread Boespflug, Mathieu
-- Forwarded message -- From: Boespflug, Mathieu Date: 13 December 2017 at 23:03 Subject: Re: Release policies To: Simon Peyton Jones Cc: ghc-devops-gr...@haskell.org [replying to ghc-devops-group@, which I assume based on your email's

Re: [GHC] #14537: Do not link to msvcrt.dll

2017-12-13 Thread Phyx
Add a -v3 to ghc to see what's happening. On Wed, Dec 13, 2017, 07:23 GHC wrote: > #14537: Do not link to msvcrt.dll > -+- > Reporter: johndoe |Owner: (none) >

Release policies

2017-12-13 Thread Simon Peyton Jones via ghc-devs
Dear GHC devops group The conversation on Trac #14558 suggests that we might want to consider reviewing GHC's release policies. This email is to invite your input. The broad