No subject
Tue Nov 30 21:47:11 CET 2010
to solve by switching is that darcs makes branching and merging very =
difficult for us. We have a few branches of HEAD that are very painful =
to keep merged with HEAD, and we would almost certainly have more =
branches if the overhead were lower. In some sense the overhead is =
self-inflicted because we have the no-conflict policy in the mainline =
repository, but that is to avoid problems with darcs' merging algorithms =
(both performance and correctness). We are still using darcs v1 patches =
rather than v2, but there are known problems with v2 which are =
preventing us from upgrading.
The darcs team have been making great strides with performance, but =
conflict handling remains a serious problem. The darcs roadmap doesn't =
show this being fixed in the near future
http://wiki.darcs.net/Roadmap
Rebase support is coming, and it does work, though the workflow is a bit =
laborious.
Besides the branching/merging/conflict issue, switching to git would =
give us plenty of side benefits, notably via access to a wealth of tool =
support. Making contribution easy is important to us too, and there are =
a lot of people using git.
The cost of switching is quite high, which is one reason we decided to =
stay with darcs last time. We have multiple repos that need to be =
converted, and for some of them, where the repo is being shared with =
other projects, we may have to mirror rather than convert in place. =
We're prepared to put in the effort if the gains would be worthwhile =
though (offers of help are more than welcome!).
We're intrested in opinions from both active and potential GHC =
developers/contributors. Let us know what you think - would this make =
life harder or easier for you? Would it make you less likely or more =
likely to contribute?
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
Cvs-ghc at haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
=20
_____ =20
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1191 / Virus Database: 1435/3370 - Release Date: 01/09/11
------=_NextPart_000_0167_01CBB0E4.2E1D5F20
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.avgcert, li.avgcert, div.avgcert
{mso-style-name:avgcert;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>As everyone has been saying, the primary issue is the workflow of the =
main contributors and the cost of the =
transition.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p> </o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>However, I made the transition to Git and GitHub earlier this year =
and that initial investment has been repaid handsomely (it=E2=80=99s the =
first system I have felt truly comfortable =
with).<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p> </o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I <i>suspect</i> a transition to Git would work out well in the long =
run and make the GHC sources more accessible.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p> </o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Chris<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p> </o:p></span></p><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
glasgow-haskell-users-bounces at haskell.org =
[mailto:glasgow-haskell-users-bounces at haskell.org] <b>On Behalf Of =
</b>Daniel Peebles<br><b>Sent:</b> 10 January 2011 15:40<br><b>To:</b> =
Simon Marlow<br><b>Cc:</b> GHC CVS list; =
glasgow-haskell-users at haskell.org<br><b>Subject:</b> Re: RFC: migrating =
to git<o:p></o:p></span></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>I fully support this (especially if it lived on =
github), but we should probably sort the top contributors to GHC in the =
past year or so and consider their opinions on the matter in that order =
:) I certainly would not be on that list. A git(hub)-based workflow =
would however facilitate any minor contributions I might make (and I'd =
imagine those of many others).<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p> </o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Dan<o:p></o:p></p><div><p =
class=3DMsoNormal>On Mon, Jan 10, 2011 at 6:19 AM, Simon Marlow <<a =
href=3D"mailto:marlowsd at gmail.com">marlowsd at gmail.com</a>> =
wrote:<o:p></o:p></p><p class=3DMsoNormal>It's time to consider again =
whether we should migrate GHC development from darcs to (probably) =
git.<br><br>From our perspective at GHC HQ, the biggest problem that we =
would hope to solve by switching is that darcs makes branching and =
merging very difficult for us. We have a few branches of HEAD that =
are very painful to keep merged with HEAD, and we would almost certainly =
have more branches if the overhead were lower. In some sense the =
overhead is self-inflicted because we have the no-conflict policy in the =
mainline repository, but that is to avoid problems with darcs' merging =
algorithms (both performance and correctness). We are still using =
darcs v1 patches rather than v2, but there are known problems with v2 =
which are preventing us from upgrading.<br><br>The darcs team have been =
making great strides with performance, but conflict handling remains a =
serious problem. The darcs roadmap doesn't show this being fixed =
in the near future<br><br> <a =
href=3D"http://wiki.darcs.net/Roadmap" =
target=3D"_blank">http://wiki.darcs.net/Roadmap</a><br><br>Rebase =
support is coming, and it does work, though the workflow is a bit =
laborious.<br><br>Besides the branching/merging/conflict issue, =
switching to git would give us plenty of side benefits, notably via =
access to a wealth of tool support. Making contribution easy is =
important to us too, and there are a lot of people using git.<br><br>The =
cost of switching is quite high, which is one reason we decided to stay =
with darcs last time. We have multiple repos that need to be =
converted, and for some of them, where the repo is being shared with =
other projects, we may have to mirror rather than convert in place. =
We're prepared to put in the effort if the gains would be worthwhile =
though (offers of help are more than welcome!).<br><br><br>We're =
intrested in opinions from both active and potential GHC =
developers/contributors. Let us know what you think - would this =
make life harder or easier for you? Would it make you less likely =
or more likely to contribute?<br><br>Cheers,<br> =
Simon<br><br>_______________________________________________<br>Cvs=
-ghc mailing list<br><a href=3D"mailto:Cvs-ghc at haskell.org" =
target=3D"_blank">Cvs-ghc at haskell.org</a><br><a =
href=3D"http://www.haskell.org/mailman/listinfo/cvs-ghc" =
target=3D"_blank">http://www.haskell.org/mailman/listinfo/cvs-ghc</a><o:p=
></o:p></p></div><p class=3DMsoNormal><o:p> </o:p></p></div><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><hr =
size=3D1 width=3D"100%" noshade style=3D'color:#A0A0A0' =
align=3Dcenter></div><p class=3Davgcert>No virus found in this =
message.<br>Checked by AVG - <a =
href=3D"http://www.avg.com">www.avg.com</a><br>Version: 10.0.1191 / =
Virus Database: 1435/3370 - Release Date: =
01/09/11<o:p></o:p></p></div></body></html>
------=_NextPart_000_0167_01CBB0E4.2E1D5F20--
More information about the Glasgow-haskell-users
mailing list