Hello,
I have been working on a GHC branch for the last few months and, for me,
switching to git would be a win because I find it quite difficult to keep my
branch and HEAD synchronized. I allocate about a day, probably about once a
month, to redo my repository so that it is in sync with HEAD.
My background is that I use many VCSes for work (although lately, mostly
git), and git for my non-work projects. I am by no means an advanced VCS
user. I do like git's graph-based non-mutable history model and it has been
the only VCS where I've been able to work out how to do something more or
less "from first principles". I don't really use the command line interface
much, I tend to use mostly tools like "gitk", and "git gui".
-Iavor
On Mon, Jan 10, 2011 at 10:46 AM, Ian Lynagh
On Mon, Jan 10, 2011 at 01:27:17PM +0000, Simon Marlow wrote:
It would be a prerequisite to switching that a GHC developer only has to use one VCS. So we either migrate dependencies to git, or mirror them in GHC-specific git branches.
I think it's hard to know how well it's going to work in advance (I was going to try redoing all the GHC 7 merges with git, but that won't tell us much if they would have been recorded differently in a git workflow), so perhaps we should change only the GHC repo at first, and see how it goes?
That way, if we decide it's worse, we haven't done a lot of work migrating dependencies or setting up mirrors, and to roll back we only need to migrate the new git patches into the old darcs repo.
Thanks Ian
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users