Hi,
I have a couple of branches of ghc off of HEAD.
I found that I had some difficulty _finding_ my patch submissions after
weeks of 'darcs_all pull -a'. And I understand that one complaint is the
need to create 'megapatches'.
How is this flow:
1) 'darcs shunt' all patches originating from thi
pgj-freebsd-amd64-stable (amd64 FreeBSD STABLE), build 129
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-amd64-stable/129.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting v
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 Tue Jan 11 18:00:01 GMT 2011.
checking out new source tree
pgj-freebsd-i386-stable (x86 FreeBSD STABLE), build 112
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-i386-stable/112.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting versi
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 Tue Jan 11 18:10:01 GMT 2011.
checking out new source tree
pgj2 (amd64 FreeBSD HEAD), build 247
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj2/247.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date | Success
booting
tn23 (x86 OSX HEAD), build 240
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/240.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date | Success
booting | Succ
pgj (x86 FreeBSD HEAD), build 249
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj/249.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date | Success
booting | Su
simonmar-win32-head (x86 Windows HEAD), build 213
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-head/213.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date | Suc
simonmar-win32-stable (x86 Windows STABLE), build 148
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-stable/148.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date
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 Tue Jan 11 18:00:01 GMT 2011.
checking out new source
Tue Jan 4 16:25:12 PST 2011 simo...@microsoft.com
* Test Trac #4870
A ./tests/ghc-regress/deSugar/should_compile/T4870.hs
A ./tests/ghc-regress/deSugar/should_compile/T4870a.hs
M ./tests/ghc-regress/deSugar/should_compile/all.T +6
View patch online:
http://darcs.haskell.org/cgi-bi
Tue Nov 16 04:50:19 PST 2010 simo...@microsoft.com
* Test Trac #4488
A ./tests/ghc-regress/deSugar/should_compile/T4488.hs
A ./tests/ghc-regress/deSugar/should_compile/T4488.stderr
M ./tests/ghc-regress/deSugar/should_compile/all.T +1
View patch online:
http://darcs.haskell.org/cgi
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 Tue Jan 11 18:10:01 GMT 2011.
checking out new s
Hello,
On Thu, Jan 06, 2011 at 11:38:13AM +, Simon Marlow wrote:
> ...
> Presumably these are failures in the fast testsuite and would show
> up in a validate, right? Any OS X folks available to take a look?
A quick look reveals:
1. A validate on tn23 results in:
> OVERALL SUMMARY for test
kgardas-opensolaris-x86-head (x86 Solaris HEAD), build 109
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/kgardas-opensolaris-x86-head/109.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setti
On 11/01/2011, at 22:20, Simon Marlow wrote:
> On 11/01/11 21:57, Roman Leshchinskiy wrote:
>> IMO, darcs-all works pretty well. I don't think I ever really had
>> problems with missing library patches.
>
> I often see problems where someone has done 'darcs pull' rather than
> './darcs-all pull'
If we put the deriving defaults together with the class definition, as normal
defaults and as op4 in your code above, we have a somewhat strange situation,
since the code for op4 can have some "extra context" not easily visible;
|minimum| could be an imported function, for instance.
A naive end
Fri Dec 3 01:48:40 PST 2010 Simon Marlow
* throwTo: report the why_blocked value in the barf()
M ./rts/RaiseAsync.c -1 +1
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=ghc-7.0/ghc;a=darcs_commitdiff;h=20101203094840-12142-061d755b6af712d16998975d81dc6233a255a864.gz
Tue Jan 4 16:27:12 PST 2011 simo...@microsoft.com
* Fix Trac #4870: get the inlining for an imported INLINABLE Id
We need the unfolding even for a *recursive* function (indeed
that's the point) and I was using the wrong function to get it
(idUnfolding rather than realIdUnfolding).
Tue Jan 11 11:48:38 PST 2011 Ian Lynagh
* Fix installation on cygwin
M ./includes/ghc.mk -4 +4
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=ghc-7.0/ghc;a=darcs_commitdiff;h=2011094838-3fd76-cbe4efc78dbb9e45af151bb6e25267e9708065de.gz
On 11/01/11 21:57, Roman Leshchinskiy wrote:
On 11/01/2011, at 21:41, Iavor Diatchki wrote:
If GHC and the libraries on which it depends were in git (migrated,
or mirrored), then we could use git sub-modules to track the
dependencies between changes to GHC and changes to the libraries.
Roughly
On 11/01/2011, at 21:41, Iavor Diatchki wrote:
> If GHC and the libraries on which it depends were in git (migrated, or
> mirrored), then we could use git sub-modules to track the dependencies
> between changes to GHC and changes to the libraries.
>
> Roughly, the workflow would be like th
Tue Jan 11 11:48:38 PST 2011 Ian Lynagh
* Fix installation on cygwin
M ./includes/ghc.mk -4 +4
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=ghc;a=darcs_commitdiff;h=2011094838-3fd76-cbe4efc78dbb9e45af151bb6e25267e9708065de.gz
On 11 January 2011 19:07, Roman Leshchinskiy wrote:
> On 11/01/2011, at 16:14, Tony Finch wrote:
>
>> On Mon, 10 Jan 2011, Roman Leshchinskiy wrote:
>>>
>>> It also seems to make finding buggy patches rather hard.
>>
>> Have a look at `git bisect`.
>
> I'm aware of git bisect. It doesn't do what I
On 11/01/2011, at 16:14, Tony Finch wrote:
> On Mon, 10 Jan 2011, Roman Leshchinskiy wrote:
>>
>> It also seems to make finding buggy patches rather hard.
>
> Have a look at `git bisect`.
I'm aware of git bisect. It doesn't do what I want. I usually have a pretty
good idea of which patch(es) m
Hi Simon,
2011/1/7 Simon Peyton-Jones
> Several thoughts
>
>
>
> First, about type families:
>
> deriving instance (Representable0 a rep, GenericEq rep) => Eq a where
> eq = genericEqDefault
>
> Didn’t we decide to use type families, in the end ? So this would be
>
>
>
> deriving instance (
On Mon, Jan 10, 2011 at 12:19 PM, Simon Marlow wrote:
> It's time to consider again whether we should migrate GHC development from
> darcs to (probably) git.
>
> From our perspective at GHC HQ, the biggest problem that we would hope to
> solve by switching is that darcs makes branching and merging
On 11/01/2011 00:36, rocon...@theorem.ca wrote:
On Mon, 10 Jan 2011, Simon Marlow wrote:
It's time to consider again whether we should migrate GHC development
from darcs to (probably) git.
From our perspective at GHC HQ, the biggest problem that we would hope
to solve by switching is that darc
29 matches
Mail list logo
