fptools mirror in darcs ready for testing
Hello everyone, Finally! Simon Marlow's plan[1] for moving from CVS to darcs for fptools, GHC, etc. is happening. Thanks to some feedback from him and the author of Tailor, as well as some free time finally, I've been able to convert things from CVS to darcs according to the plan. So, the first phase is to have live, updated darcs mirrors of CVS repos as appropriate. We now have that. Please feel free to darcs get --partial any of these. (Trust me, you *REALLY* want to use --partial. You'd be downloading over 13,000 patches otherwise on some of these.) http://cvs.haskell.org/darcs/ghc GHC HEAD http://cvs.haskell.org/darcs/ghc.ghc-6.4 GHC ghc-6-4-branch http://cvs.haskell.org/darcs/libraries libraries dir from fptools, HEAD http://cvs.haskell.org/darcs/libraries.ghc-6.4 libraries dir from fptools, ghc-6-4-branch http://cvs.haskell.org/darcs/nofib nofib dir from fptools, HEAD (there were no commits on ghc-6-4-branch for nofib) http://cvs.haskell.org/darcs/testsuite testsuite dir from fptools, HEAD http://cvs.haskell.org/darcs/testsuite.ghc-6.4 testsuite dir from fptools, ghc-6-4-branch Please note that you cannot pull patches between branches. This is because it is not really possible to have an automated CVS to darcs conversion that preserves enough information to do so. However, once the 6.4 branches go away, this will become nicely possible with future branches. Also please note that these repos are READ ONLY for now. Nobody will be accepting darcs patches until Simon (or someone) gives the word. These will all be updating daily as soon as I get around to writing a cron job. [1] http://www.haskell.org//pipermail/cvs-ghc/2005-November/027174.html
Hooray!! Thanks John jgoerzen:
Hello everyone,
Finally! Simon Marlow's plan[1] for moving from CVS to darcs for fptools, GHC, etc. is happening. Thanks to some feedback from him and the author of Tailor, as well as some free time finally, I've been able to convert things from CVS to darcs according to the plan.
So, the first phase is to have live, updated darcs mirrors of CVS repos as appropriate. We now have that.
Please feel free to darcs get --partial any of these. (Trust me, you *REALLY* want to use --partial. You'd be downloading over 13,000 patches otherwise on some of these.)
http://cvs.haskell.org/darcs/ghc GHC HEAD http://cvs.haskell.org/darcs/ghc.ghc-6.4 GHC ghc-6-4-branch http://cvs.haskell.org/darcs/libraries libraries dir from fptools, HEAD http://cvs.haskell.org/darcs/libraries.ghc-6.4 libraries dir from fptools, ghc-6-4-branch http://cvs.haskell.org/darcs/nofib nofib dir from fptools, HEAD (there were no commits on ghc-6-4-branch for nofib) http://cvs.haskell.org/darcs/testsuite testsuite dir from fptools, HEAD http://cvs.haskell.org/darcs/testsuite.ghc-6.4 testsuite dir from fptools, ghc-6-4-branch
Please note that you cannot pull patches between branches. This is because it is not really possible to have an automated CVS to darcs conversion that preserves enough information to do so. However, once the 6.4 branches go away, this will become nicely possible with future branches.
Also please note that these repos are READ ONLY for now. Nobody will be accepting darcs patches until Simon (or someone) gives the word.
These will all be updating daily as soon as I get around to writing a cron job.
[1] http://www.haskell.org//pipermail/cvs-ghc/2005-November/027174.html _______________________________________________ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
On Wed, 2005-11-30 at 14:49 -0600, John Goerzen wrote:
Hello everyone,
Finally! Simon Marlow's plan[1] for moving from CVS to darcs for fptools, GHC, etc. is happening. Thanks to some feedback from him and the author of Tailor, as well as some free time finally, I've been able to convert things from CVS to darcs according to the plan.
[..]
Also please note that these repos are READ ONLY for now. Nobody will be accepting darcs patches until Simon (or someone) gives the word.
When that does happen, it'd be great if the repos specified a default 'darcs send' email address so that people do not have to guess where to send their patches. (At the moment darcs prompts me for where to send the patches) I expect the right address will be one of the ghc lists, either cvs or bugs. Duncan
On Wed, Dec 07, 2005 at 11:02:29AM +0000, Duncan Coutts wrote:
Also please note that these repos are READ ONLY for now. Nobody will be accepting darcs patches until Simon (or someone) gives the word.
When that does happen, it'd be great if the repos specified a default 'darcs send' email address so that people do not have to guess where to send their patches.
Yes, they will. Simon is thinking of having that be the appropriate cvs-*@haskell.org list. Right now, this isn't happening because there is no good place to send them. Speaking of which: how long do we want to keep this interim arrangement before switching to darcs completely? -- John
On Wed, 2005-12-07 at 07:05 -0600, John Goerzen wrote:
On Wed, Dec 07, 2005 at 11:02:29AM +0000, Duncan Coutts wrote:
Also please note that these repos are READ ONLY for now. Nobody will be accepting darcs patches until Simon (or someone) gives the word.
When that does happen, it'd be great if the repos specified a default 'darcs send' email address so that people do not have to guess where to send their patches.
Yes, they will. Simon is thinking of having that be the appropriate cvs-*@haskell.org list. Right now, this isn't happening because there is no good place to send them.
Speaking of which: how long do we want to keep this interim arrangement before switching to darcs completely?
That's up to Simon and Simon of course but in my experience with Gtk2Hs (which is in transition from cvs to darcs too) you only really get the advantages of darcs when you fully switch. I guess that's an obvious point but part of the advantage is just having the darcs mirror available for users/testers/contributers. Since setting up the Gtk2Hs darcs mirror we've had many more people using and testing the development version (eg verifying bug fixes that we make). This has been a great benefit to the quality of our releases. However the process for receiving a darcs patch and then converting that so that it can be applied to the cvs master repo is a bit of a pain. So the benefit of fully moving to darcs will mostly be for the core ghc developers. Duncan
http://cvs.haskell.org/darcs/ghc http://cvs.haskell.org/darcs/libraries
It suddenly occurs to me that there are other projects in CVS that have not yet been converted to darcs, e.g. Hugs98 and nhc98. Are there plans to do so? If not, then since both of these depend on the libraries tree, there will need to be some other plan to cope with the eventual dropping of the libraries CVS archive. There are also a bunch of other smaller, more stand-alone projects like cpphs, hat, ohugs, programmatica, timber. The long-term plan for Hat is to depend on the libraries tree, although it does not do so currently. Hugs98 and nhc98 both currently depend on cpphs. Regards, Malcolm
participants (4)
-
dons＠cse.unsw.edu.au -
Duncan Coutts -
John Goerzen -
Malcolm Wallace