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