On 2008 Aug 10, at 2:12, Jason Dagit wrote:
On Sat, Aug 9, 2008 at 10:44 PM, Roman Leshchinskiy <[EMAIL PROTECTED]
> wrote:
Maybe investing some time in fixing the most obvious darcs problems
would be a better solution?
We're working on that over at Darcs HQ, but there is no guarantee
th
On Sat, Aug 9, 2008 at 10:44 PM, Roman Leshchinskiy <[EMAIL PROTECTED]>wrote:
Maybe investing some time in fixing the most obvious darcs problems would be
> a better solution?
We're working on that over at Darcs HQ, but there is no guarantee that we'd
come close to fixing the problems within the
On 10/08/2008, at 05:38, Don Stewart wrote:
Instead, if we just use ubiquitous, common tools -- like git -- for
everything, we minimise the pain for people, and sit firmly in the
mainstream of open source.
While I agree with this in general, I'm not sure it really applies to
vcs (especially
On 10/08/2008, at 14:40, Manuel M T Chakravarty wrote:
Personally, I am more than happy to stay with darcs, too, but my
understanding was that at least the Simons decided that we are going
to move from darcs to git. All I am saying is that whatever vcs ghc
uses, you need to be able to *ea
Listen to Don, he is a wise man!
Manuel
Don Stewart:
I agree with this.
As Audrey says, you have to lower the barrier to entry. That means:
* one build system
* one vcs
to build ghc (and anything it requires, such as the core libraries).
This is a chance to make a big step towards acc
Ian Lynagh:
On Sat, Aug 09, 2008 at 03:46:50PM +1000, Manuel M T Chakravarty
wrote:
I am not talking about all libs, I am talking about the core libs.
Most developers of the core libs are also GHC developers.
I'm not sure that's true. e.g. Malcolm and Ross both commit to the
bootlibs, and we
Isaac Dupree:
Duncan Coutts wrote:
On Sat, 2008-08-09 at 15:46 +1000, Manuel M T Chakravarty wrote:
Raising the bar for developers to contribute to a project has
been proven to be a very bad idea many times. Let's not take GHC
down that path.
I don't especially relish having to learn ano
Duncan Coutts:
On Sat, 2008-08-09 at 15:46 +1000, Manuel M T Chakravarty wrote:
Raising the bar for developers to contribute to a project has been
proven to be a very bad idea many times. Let's not take GHC down
that
path.
I don't especially relish having to learn another vcs tool or rais
As a very part-time, temporarily inactive GHC developer I will offer
some opinions which should carry no weight:
* When I saw the announcement, I cheered! Last fall, I lost 2 weeks
of a 9-week visit to darcs hell. While the alleged features may
be alluring, the software simply doesn't
I seriously hope the plan is to move all *core* libraries
(including
GHC's cabal repo) etc over to git, too.
* one build system
* one vcs
This is a chance to make a big step towards accessibility, let's
make that step.
Ultimately, I don't think git would make ghc any more accessible
dons:
> chak:
> > Ian Lynagh:
> > >On Fri, Aug 08, 2008 at 12:04:15PM +1000, Manuel M T Chakravarty
> > >wrote:
> > >>
> > >>I seriously hope the plan is to move all *core* libraries (including
> > >>GHC's cabal repo) etc over to git, too. In other word, everything
> > >>that you need to build t
chak:
> Ian Lynagh:
> >On Fri, Aug 08, 2008 at 12:04:15PM +1000, Manuel M T Chakravarty
> >wrote:
> >>
> >>I seriously hope the plan is to move all *core* libraries (including
> >>GHC's cabal repo) etc over to git, too. In other word, everything
> >>that you need to build the development version
On Sat, Aug 09, 2008 at 03:46:50PM +1000, Manuel M T Chakravarty wrote:
>
> Don was excited about getting more people to look at the source
> when it is in git (see the comments he posted from reddit).
I am skeptical that this initial excitement and cloning will translate
into more developers.
On Sat, Aug 09, 2008 at 01:32:51AM +0100, Duncan Coutts wrote:
>
> If there's some way of having automated git mirrors of the upstream
> darcs repos then that's might be convenient for people building ghc.
I don't think that that really helps. If all you want to do is build
then the sync-all scri
Duncan Coutts wrote:
On Sat, 2008-08-09 at 15:46 +1000, Manuel M T Chakravarty wrote:
Raising the bar for developers to contribute to a project has been
proven to be a very bad idea many times. Let's not take GHC down that
path.
I don't especially relish having to learn another vcs tool o
On Sat, 2008-08-09 at 15:46 +1000, Manuel M T Chakravarty wrote:
> Raising the bar for developers to contribute to a project has been
> proven to be a very bad idea many times. Let's not take GHC down that
> path.
I don't especially relish having to learn another vcs tool or raising
the bar
16 matches
Mail list logo
