Build description = STABLE on i386-unknown-linux (cam-02-unx)
Build location= /playpen/simonmar/nightly/STABLE
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Thu May 19 18:10:01 BST 2011.
checking out new source tree
Build description = HEAD on i386-unknown-linux (cam-02-unx)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Thu May 19 18:00:01 BST 2011.
checking out new source tree
Build description = STABLE on x86_64-unknown-linux (cam-04-unx)
Build location= /64playpen/simonmar/nightly/STABLE-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-04-unx
Nightly build started on cam-04-unx at Thu May 19 18:10:01 BST 2011.
checking out new s
Build description = HEAD on x86_64-unknown-linux (cam-04-unx)
Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx
Nightly build started on cam-04-unx at Thu May 19 18:00:01 BST 2011.
checking out new source
Repository : ssh://darcs.haskell.org//srv/darcs/haddock2
Branch 'ghc-generics' now includes:
1d81436... Wibbles for ghc-new-co branch
797ab27... Merge remote branch 'origin/master' into ghc-new-co
6df3a04... Follow changes in SDoc
89813e7... Merge branch 'ghc-new-co'
28df
Repository : ssh://darcs.haskell.org//srv/darcs/haddock2
On branch : ghc-generics
http://hackage.haskell.org/trac/ghc/changeset/6f92cdd12d1354dfbd80f8323ca333bea700896a
>---
commit 6f92cdd12d1354dfbd80f8323ca333bea700896a
Merge: f420c
| I'd like to set some expectations here. My current belief is that the
| process that's used to managed e.g. bytestring, text, and network is
| fine. That is the default the-maintainer-knows-what-he's-doing open
| source approach
Indeed. That's what we intended by the "trust the maintainer"
| I don't have access to a Windows box, so *I* cannot ensure the code runs on
| Windows.
| And if the code involved doesn't make use of any OS-specific functions or
| libraries, like purely numerical code in base, if it worked on one OS but
| not on another, something lying deeper would be bro
On Thu, May 19, 2011 at 2:18 PM, Simon Peyton-Jones
wrote:
> No, we intended that the maintainer is never *required* to accept a change.
> To quote "the community offers opinions; the maintainer decides". If you
> think that point should be made even more strongly, can you go ahead and edit?
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/279dd43b9b7ab87e6ec83aa00f93d27bdadeb6fc
>---
commit 279dd43b9b7ab87e6ec83aa00f93d27bdadeb6fc
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/27a6ce916b2eb2662bf3daafe6e3cb0f94e081b5
>---
commit 27a6ce916b2eb2662bf3daafe6e3cb0f94e081b5
Author: Johan Tib
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/7338cdad971cb1a8e9d0c24f9bd2444cfd1fd97a
>---
commit 7338cdad971cb1a8e9d0c24f9bd2444cfd1fd97a
Author: Johan Tib
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/9c23f06f3eb925dca063d5102b0ced4a9afe795e
>---
commit 9c23f06f3eb925dca063d5102b0ced4a9afe795e
Author: Johan Tibell
D
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/a6cc4146630e34f2d69c5a0358a9133420f9102c
>---
commit a6cc4146630e34f2d69c5a0358a9133420f9102c
Author: Daniel Peebles
Johan Tibell wrote:
>
> It's not clear when the "deadline for discussion" should be used. Does
> it apply to any change or only public API changes? Does it apply even if
> it's the maintainer that making the change? Having to spent two weeks
> (even though most of the time is spent waiting) to make
On 19/05/2011 10:47, Johan Tibell wrote:
Section 3:
It's not clear when the "deadline for discussion" should be used. Does
it apply to any change or only public API changes? Does it apply even
if it's the maintainer that making the change? Having to spent two
weeks (even though most of the time
[Changing subject line; sorry for the odd initial one!]
| "widespread support" is a bit of a wishy-washy phrase. If 7 people
| want it, is that widespread support?
| ...should be added. However, there's a strong selection bias here and
| ...This is one of the places where having a real maintainer
dead right; fixed
| -Original Message-
| From: Ivan Lazar Miljenovic [mailto:ivan.miljeno...@gmail.com]
| Sent: 19 May 2011 13:14
| To: Simon Peyton-Jones
| Cc: Haskell Libraries; cvs-ghc@haskell.org; Daniel Fischer
| Subject: Re: Proposal: Make gcd total
|
| On 19 May 2011 18:35, Simon P
Edward Z. Yang wrote:
> What might also be pretty useful is a global "checkout a commit from
> before this time",
I believe this to be doable. I'm working on a tool for it.
> which would also work even in the case of missing
> build logs (we should also publish a log of build log hashes, so you
What might also be pretty useful is a global "checkout a commit from
before this time", which would also work even in the case of missing
build logs (we should also publish a log of build log hashes, so you
can have some record of known good builds). One would have to deal with
merges, but if the
On Thu, May 19, 2011 at 10:35 AM, Simon Peyton-Jones
wrote:
> | > So if someone actually follows through with this as an official
> | > libraries submission (with a patch, deadline, etc.), the odds seem in
> | > favor of it.
> |
> | I'll try to see it through, although the process seems rather dau
Thanks! Now I have sense about the switching.
There are more confusion. Please help me make it clear:)
See this words in the quotation:
"If the foreign call is short, we don't want to incur the cost of a
context switch on returning"
-> "but since we marked the Capability as free there's a good chan
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/febf1ced754a3996ac1a5877dcded87828560d1c
>---
commit febf1ced754a3996ac1a5877dcded87828560d1c
Merge: b6264a6... 58339
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/7c185cd2525a20dcfa9859c5e6cf2f6300a19cc1
>---
commit 7c185cd2525a20dcfa9859c5e6cf2f6300a19cc1
Merge: febf1ce... 173c4
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/b6264a6b8a8e22e24464da39ca0a3a0176d91f4e
>---
commit b6264a6b8a8e22e24464da39ca0a3a0176d91f4e
Author: Dimitrios Vytin
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/9591547fbbdf12728884e125f8ba08b0e6e69f82
>---
commit 9591547fbbdf12728884e125f8ba08b0e6e69f82
Author: Dimitrios Vytin
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/8e2601adf68194abd45ea7b3df84c5436909f0a6
>---
commit 8e2601adf68194abd45ea7b3df84c5436909f0a6
Merge: 7bd5f07...
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/7bd5f076dd6f58eb856c97cc52520f377434cb76
>---
commit 7bd5f076dd6f58eb856c97cc52520f377434cb76
Author: Dimitrios
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/6804d94c8c2e80b4057f701782c03b1aac529980
>---
commit 6804d94c8c2e80b4057f701782c03b1aac529980
Merge: 508d58b...
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/508d58b78846eb09eee0ae13bb0137acfab535dd
>---
commit 508d58b78846eb09eee0ae13bb0137acfab535dd
Author: Dimitrios
On 13/05/2011 23:32, Karel Gardas wrote:
I'm attempting to make ARM registerised build reality just for own fun
(and thanks to help and encouragement provided by David Terei) and for
this I'm writing platform specific StgRun/StgReturn functions as
required in rts/StgCRun.c. I'm not sure I've go
On 19/05/2011 02:52, 吴兴博 wrote:
Hello everyone, I'm new to here, I had a question about RTS Scheduler.
When I read through the GHC Wiki commentary on the scheduler I was
confused about this section:
"""
One reason behind marking a Capability as free when it is handed
over is to support fast
| > So if someone actually follows through with this as an official
| > libraries submission (with a patch, deadline, etc.), the odds seem in
| > favor of it.
|
| I'll try to see it through, although the process seems rather daunting.
| It has annoyed me for too long.
I think there is general agr
On 18/05/2011 11:41, Karel Gardas wrote:
On 05/18/11 12:09 PM, Simon Marlow wrote:
The real difficulty with the ghc sources is that fact that
over a dozen different trees, with independant commit histories
are needed to retrieve a working revision.
Right, this is something that would be fixed
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/173c408981adb7d7b4f35d466c984d13f5d1194f
>---
commit 173c408981adb7d7b4f35d466c984d13f5d1194f
Author: Simon Marlow
D
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/58532eb46041aec8d4cbb48b054cb5b001edb43c
>---
commit 58532eb46041aec8d4cbb48b054cb5b001edb43c
Author: Spencer Janssen
36 matches
Mail list logo
