pgj-freebsd-amd64-stable (amd64 FreeBSD STABLE), build 131
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-amd64-stable/131.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions
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 Jan 13 18:00:01 GMT 2011.
checking out new source tree
pgj-freebsd-i386-stable (x86 FreeBSD STABLE), build 114
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-i386-stable/114.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions | S
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 Jan 13 18:10:01 GMT 2011.
checking out new source tree
pgj2 (amd64 FreeBSD HEAD), build 249
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj2/249.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions | Success
setting version date | Succ
simonmar-win32-head (x86 Windows HEAD), build 215
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-head/215.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions | Success
set
simonmar-win32-stable (x86 Windows STABLE), build 150
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-stable/150.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions | Succe
pgj (x86 FreeBSD HEAD), build 251
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj/251.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions | Success
setting version date | Success
tn23 (x86 OSX HEAD), build 242
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/242.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions | Success
setting version date | Success
bo
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 Jan 13 18:00:01 GMT 2011.
checking out new source
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 Jan 13 18:10:01 GMT 2011.
checking out new s
kgardas-opensolaris-x86-head (x86 Solaris HEAD), build 111
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/kgardas-opensolaris-x86-head/111.html
darcs checkout| Success
create mk/build.mk| Success
get subrepos | Success
repo versions
On 14 January 2011 10:58, Isaac Dupree wrote:
> On 01/13/11 08:42, Eric Kow wrote:
>
>> On Wed, Jan 12, 2011 at 15:49:31 -0500, Isaac Dupree wrote:
>>
>>> What if "pull" could (maybe given a flag that you'd use with your
>>> upstream) re-order all patches from upstream, new or old, as far
>>> back
On 01/13/11 08:42, Eric Kow wrote:
On Wed, Jan 12, 2011 at 15:49:31 -0500, Isaac Dupree wrote:
What if "pull" could (maybe given a flag that you'd use with your
upstream) re-order all patches from upstream, new or old, as far
back in your history as possible?
I'm always nervous about introduci
On 01/13/2011 12:49 AM, Simon Marlow wrote:
> I spent quite some time yesterday playing with submodules to see if they
> would work for GHC. I'm fairly sure there are no fundamental reasons that
> we couldn't use them, but there are enough gotchas to put me off. I wrote
> down what I discovered he
On 12 January 2011 22:13, Claus Reinke wrote:
>> You can emulate darcs's patch re-ordering in git if you put each
>> independent sequence of patches on a separate branch. Then you can
>> re-merge the branches in whatever order you want. This is a fairly
>> common git workflow.
>
> What happens aft
On Thu, Jan 13, 2011 at 4:03 PM, Simon Marlow wrote:
> I've made git mirrors of the current GHC HEAD repos (all of them), so people
> can try out their workflows with git.
Poking around in the different repos works for me and is fast. For example:
Find new files in base:
$ cd libraries/base
$ g
I've made git mirrors of the current GHC HEAD repos (all of them), so
people can try out their workflows with git. Hopefully this should work:
git clone http://darcs.haskell.org/ghc-git/ghc.git
cd ghc
perl sync-all get
You have to use sync-all instead of darcs-all, but the syntax is the
Thu Jan 13 05:11:47 PST 2011 Simon Marlow
* fix for remote repos without -r
M ./sync-all -13 +13
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=ghc;a=darcs_commitdiff;h=20110113131147-12142-0252565ea150652fb8c180c55b35e3ff364410b0.gz
__
Thu Jan 13 03:16:54 PST 2011 Simon Marlow
* add the -r flag from darcs-all
M ./sync-all -42 +124
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=ghc;a=darcs_commitdiff;h=20110113111654-12142-307446a4cfd81955b870fe1676dd0200ba6fd89d.gz
__
Thu Jan 13 03:17:33 PST 2011 Simon Marlow
* add a version of packages that stores all the repos in git
A ./packages.git
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=ghc;a=darcs_commitdiff;h=20110113111733-12142-c82cda678177062f018fe93603aa881b5234b0d0.gz
___
Thu Jan 13 03:14:53 PST 2011 simo...@microsoft.com
* Track changes to the finder's error messages
M ./tests/ghc-regress/driver/driver063.stderr -2 +2
M ./tests/ghc-regress/ghc-e/should_run/2636.stderr -2 +2
M ./tests/ghc-regress/ghci.debugger/scripts/dynbrk001.stderr -2 +2
M ./t
Thu Jan 13 03:58:46 PST 2011 simo...@microsoft.com
* Track recent changes in error messages
M ./tests/ghc-regress/driver/recomp006/recomp006.stderr -1 +1
M ./tests/ghc-regress/ghc-api/apirecomp001/apirecomp001.stderr -6 +6
M ./tests/ghc-regress/indexed-types/should_fail/T3330a.stder
Thu Jan 13 03:14:21 PST 2011 simo...@microsoft.com
* Make Template Haskell classInstances function return [ClassInstance]
This is a recently-introduce function, which was returning
a [Name], being the names of the dfuns. But what you really
want (obviously!) is the ClassInstances, and
Thu Jan 13 01:39:31 PST 2011 simo...@microsoft.com
* White space only
M ./compiler/typecheck/TcRnTypes.lhs -1 +1
M ./compiler/typecheck/TcSimplify.lhs +5
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=ghc;a=darcs_commitdiff;h=20110113093931-1287e-f57503c836dd7f1a622
Thu Jan 13 03:12:33 PST 2011 simo...@microsoft.com
* Improve the finder's error messages
I'd done all the work to add fuzzy-match suggestions, but they
weren't really being used! Here's what you get now
module Foo where
import Data.Lst
Foo.hs:3:1:
Failed to load
So, for the purposes of the new generic deriving mechanism, "deriving" clauses
attached to a datatype or standalone deriving will not be affected.
Correct. "Deriving" clauses simply generate boilerplate code, and can continue
to do so.
Generic instances are derived using instance declarations w
Ok, so I think we reached a possible solution here. Summarizing: for a class
C
class (Ctx1) => C a where
> noDef :: a
>
> h98Def :: a
> h98Def = ...
>
> genDef :: a
> generic genDef :: (Ctx2) => a
> genDef = ...
>
instances are defined like this:
instance C T where
> noDef = ... --
On 13 January 2011 08:54, Roman Leshchinskiy wrote:
> On 12 Jan 2011, at 23:31, "Edward Z. Yang" wrote:
>
>> Excerpts from Roman Leshchinskiy's message of Wed Jan 12 18:20:25 -0500 2011:
>>> How would we get the current functionality of darcs-all pull? Is it even
>>> possible?
>>
>> Here is the
On 12 Jan 2011, at 23:31, "Edward Z. Yang" wrote:
> Excerpts from Roman Leshchinskiy's message of Wed Jan 12 18:20:25 -0500 2011:
>> How would we get the current functionality of darcs-all pull? Is it even
>> possible?
>
> Here is the rebase-y workflow.
Thank you making things clearer!
>>
>
On 12/01/2011 22:22, Iavor Diatchki wrote:
Hello,
On Wed, Jan 12, 2011 at 11:44 AM, Roman Leshchinskiy mailto:r...@cse.unsw.edu.au>> wrote:
On 12/01/2011, at 09:22, Simon Marlow wrote:
> On 11/01/2011 23:11, Roman Leshchinskiy wrote:
>>
>> A quick look at the docs seems to i
31 matches
Mail list logo
