Re: [GHC] #1114: Socket code dies with SIGPIPE

#1114: Socket code dies with SIGPIPE +--- Reporter: guest | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: hslibs/net |

[GHC] #1114: Socket code dies with SIGPIPE

#1114: Socket code dies with SIGPIPE ---+ Reporter: guest | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: hslibs/net | Versi

[GHC] #1113: GHCi 6.6 and unicode at the REPL

#1113: GHCi 6.6 and unicode at the REPL --+- Reporter: [EMAIL PROTECTED] | Owner: Type: bug| Status: new Priority: normal | Milestone:

Re: [GHC] #1100: Parse error on (#) in .lhs files

#1100: Parse error on (#) in .lhs files +--- Reporter: [EMAIL PROTECTED] | Owner: Type: bug | Status: new Priority: low | Milestone:

Re: [GHC] #1112: The testsuite setup is broken

No, it was not 6.6, it was HEAD. So at a minimum, I think that the summary of a log from the nightly run should be checked in together with the source of the tests. The fact that there are 0 failures for a release is of very little interest. If you are going to do any GHC development you are li

Re: [GHC] #1103: Japanese Unicode

#1103: Japanese Unicode -+-- Reporter: humasect | Owner: Type: bug | Status: new Priority: normal

Re: [GHC] #1112: The testsuite setup is broken

#1112: The testsuite setup is broken --+- Reporter: guest | Owner: Type: bug | Status: closed Priority: normal| Milestone: Component: Compiler |Version

Re: [GHC] #831: GHCi user interface bug

#831: GHCi user interface bug -+-- Reporter: guest| Owner: Type: bug | Status: new Priority: low | Milestone: 6.6.1 Component: GHCi |Version: 6.4.2

Re: [GHC] #1100: Parse error on (#) in .lhs files

#1100: Parse error on (#) in .lhs files +--- Reporter: [EMAIL PROTECTED] | Owner: Type: bug | Status: new Priority: low | Milestone: