I tweeted. Hopefully we get some feedback on this. After the Turkey dinners of course ;)<br><br>-Dan<br><br><div class="gmail_quote">On Wed, Nov 25, 2009 at 8:21 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I've imported Weld core trunk into both GitHub <a href="http://github.com/pmuir/weld-test" target="_blank">http://github.com/pmuir/weld-test</a> and BitBucket: <a href="http://bitbucket.org/pmuir/weld-test/" target="_blank">http://bitbucket.org/pmuir/weld-test/</a> for people to play with.<br>
<br>
Both these repos will be dropped once we make a decision, so treat them as playgrounds only!<br>
<font color="#888888"><br>
Pete<br>
</font><div><div></div><div class="h5"><br>
On 25 Nov 2009, at 13:07, Mark Struberg wrote:<br>
<br>
> Another strong point for using GIT is the Gerrit source review system.<br>
> It makes contributing patches easier, and much more: it makes _applying_ those contributions even easier.<br>
><br>
> LieGrue,<br>
> strub<br>
><br>
> --- Pete Muir <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>> schrieb am Mi, 25.11.2009:<br>
><br>
>> Von: Pete Muir <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>><br>
>> Betreff: Re: [seam-dev] Mercurial vs GIT<br>
>> An: "Daniel Roth" <<a href="mailto:daniel@danielroth.se">daniel@danielroth.se</a>><br>
>> CC: "<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a>" <<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a>><br>
>> Datum: Mittwoch, 25. November 2009, 13:43<br>
>> I can certainly see that a DVCS might<br>
>> not be a good fit for closed source / in company software<br>
>> development. All the work an engineer on the project does is<br>
>> likely to make it into the project at some point (even if<br>
>> heavily refactored), and they are unlikely to want to share<br>
>> it with many other people before it goes into VCS.<br>
>><br>
>> However if you consider Seam, then there are often cases<br>
>> where someone is maintaining a patch for months or even<br>
>> years against trunk which they want to easily share with<br>
>> other users. As we move towards to a more modular approach,<br>
>> this becomes even more apparent - you might want to develop<br>
>> a module outside the Seam master, and share it with the<br>
>> community. At some point we might add it to the master. I<br>
>> believe a DVCS is ideally suited to this.<br>
>><br>
>> Pete<br>
>><br>
>> On 24 Nov 2009, at 22:22, Daniel Roth wrote:<br>
>><br>
>>> 1) I have not tried GIT...<br>
>>> 2) Comparing Mercurial and SVN, for me, is like<br>
>> comparing an nightmare and ease of use.<br>
>>><br>
>>> There is a Mercurial plugin for Eclipse, but it's<br>
>> really no good. We experienced some bugs at work with it<br>
>> (DivideByZero), submitted a patch but... Still nothing has<br>
>> happened... I've tried meld, kdiff3 and the tortoise thingy<br>
>> for windows, but still I always end up with command line<br>
>> because things don't work. Also there is really no good way<br>
>> of branching. Named branches is a MESS so even the hg team<br>
>> thinks it's better to crete to different clones and then<br>
>> manually merge them. (See their manual)<br>
>>><br>
>>> One other thing I'd like to say is that having a<br>
>> distr. repo may sound really fancy, but it's rarely needed.<br>
>> Although being spread over different offices all over the<br>
>> world, that feature is never really needed at my work. And<br>
>> the really really really few times it is, you could just as<br>
>> well make an ordinary patch, and give it to the other<br>
>> person. However, there have been many times when hours has<br>
>> been wasted when trying to resolve issues when two people<br>
>> have worked in our root repo at the same time.<br>
>>><br>
>>> Just my 10 öre...<br>
>>><br>
>>> Daniel<br>
>>><br>
>>><br>
>>> On Tue, Nov 24, 2009 at 11:00 PM, Stuart Douglas<br>
>> <<a href="mailto:stuart@baileyroberts.com.au">stuart@baileyroberts.com.au</a>><br>
>> wrote:<br>
>>> As I understand it GIT support on windows is not good,<br>
>> and also just having a quick google around it looks like the<br>
>> tooling support is not very mature either. Also the commands<br>
>> are different to subversions commands so there is quite a<br>
>> steep learning curve.<br>
>>> I like bazaar, it uses the same commands as<br>
>> subversion, works on all platforms and has eclipse and<br>
>> windows support. It also has launchpad, which is the bzr<br>
>> equivalent of github.<br>
>>><br>
>>> Stuart<br>
>>> ________________________________________<br>
>>> From: <a href="mailto:seam-dev-bounces@lists.jboss.org">seam-dev-bounces@lists.jboss.org</a><br>
>> [<a href="mailto:seam-dev-bounces@lists.jboss.org">seam-dev-bounces@lists.jboss.org</a>]<br>
>> On Behalf Of Francisco Jose Peredo [<a href="mailto:franciscoperedo@tabasco.gob.mx">franciscoperedo@tabasco.gob.mx</a>]<br>
>>> Sent: Wednesday, 25 November 2009 1:17 AM<br>
>>> To: <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>>> Cc: <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
>>> Subject: Re: [seam-dev] Mercurial vs GIT<br>
>>><br>
>>> I have not tried GIT, but from what I have read it is<br>
>> pretty complicated<br>
>>> to learn to use...<br>
>>> OTOH I have tried Mercurial, which is also<br>
>> distributed, and found it<br>
>>> confortable... apparently the<br>
>>> way it deals with its distribute nature is easier for<br>
>> subversion users<br>
>>> to understand...<br>
>>> AFAIK Netbeans source code is in Mercurial, also<br>
>> OpenJDK... So it seems<br>
>>> to work<br>
>>> well with large code bases... and there are plugins<br>
>> for Netbeans,<br>
>>> Eclipse and the Tortoise Hg<br>
>>> project is advanced and usable...<br>
>>> Google Code offers free Mercurial hosting...<br>
>>> Why not Mercurial?<br>
>>><br>
>>><br>
>>><br>
>>> Pete Muir escribió:<br>
>>>> A quick item we discussed at the f2f meeting was<br>
>> whether to switch to<br>
>>>> GIT for our SCM, rather than SVN.<br>
>>>><br>
>>>> This would give us a IMO a system well suited to<br>
>> our distribued dev<br>
>>>> model, it would also make it much easier for<br>
>> others to sandbox PEs and<br>
>>>> then contribute them back to us.<br>
>>>><br>
>>>> The proposal is to use Github to host.<br>
>>>><br>
>>>> The team members at devoxx were in favour, but<br>
>> what do others think?<br>
>>>><br>
>>>> Pete<br>
>>>><br>
>>>> --<br>
>>>> Pete Muir<br>
>>>> <a href="http://in.relation.to/Bloggers/Pete" target="_blank">http://in.relation.to/Bloggers/Pete</a><br>
>>>> _______________________________________________<br>
>>>> seam-dev mailing list<br>
>>>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Dirección Informática de Servicios Financieros<br>
>>> Dirección General de Modernización e Innovación<br>
>> Gubernamental<br>
>>> Secretaría de Administración y Finanzas<br>
>>> Paseo de la Sierra 435 col. Reforma<br>
>>> C.P. 86086, Villahermosa, Tabasco.<br>
>>> Tel. 52 + 993 + 310 40 00 Ext. 7127<br>
>>> <a href="http://saf.tabasco.gob.mx/" target="_blank">http://saf.tabasco.gob.mx/</a><br>
>>><br>
>>> IMPORTANTE: Esta transmisión electrónica, incluyendo<br>
>> sus anexos, archivos insertados o "attachments", puede<br>
>> constituir información confidencial o reservada, en los<br>
>> términos de la Ley de Acceso a la Información Pública del<br>
>> Estado de Tabasco, y estar protegida por el derecho<br>
>> fundamental a la privacidad. Se prohibe el uso de esta<br>
>> información por cualquier persona distinta al receptor<br>
>> intencional o previsto. Si usted ha recibibido esta<br>
>> transmisión electrónica por error, por favor responda<br>
>> inmediatamente al emisor y borre esta información de su<br>
>> sistema. El uso, diseminación, distribución o<br>
>> reproducción de esta transmisión electrónica por<br>
>> receptores no intencionados o no previstos por el emisor, no<br>
>> está autorizada y puede considerarse ilícita en los<br>
>> términos de la legislación penal y civil vigente.<br>
>>><br>
>>> _______________________________________________<br>
>>> seam-dev mailing list<br>
>>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>>><br>
>>> _______________________________________________<br>
>>> seam-dev mailing list<br>
>>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Daniel Roth<br>
>>> M.Sc. Computer Science<br>
>>> <a href="mailto:daniel@danielroth.se">daniel@danielroth.se</a><br>
>>> <a href="http://www.danielroth.se" target="_blank">www.danielroth.se</a><br>
>>> +46 736 36 29 46<br>
>>> _______________________________________________<br>
>>> seam-dev mailing list<br>
>>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> seam-dev mailing list<br>
>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>><br>
><br>
> __________________________________________________<br>
> Do You Yahoo!?<br>
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.<br>
> <a href="http://mail.yahoo.com" target="_blank">http://mail.yahoo.com</a><br>
<br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>