mercurialeclipse status (was: hg outgoing performance: bug or design limitation?)

[Bastian Doetsch]

> Actually the mercurialeclipse repo at
> http://bitbucket.org/mercurialeclipse
> has merged in all changes from http://javaforge.com/project/HGE except for
> the namechange (Done by Bastian a few days ago) and has some other newer
> stuff. So the mercurialeclipse repos is currently little bit newer...
>
> Currently there is not much active development on mercurialeclipse
> other then the Intland clone and the mercurialeclispe release sites
> will probably just point out the Intland update-download site when
> 1.5 is released by them. I think the question is more like why they
> changed the name but hopefully that can be fixed before the final
> 1.5 as it confuses people alot that it is something different then
> mercurialeclipse.
>

I don't understand the naming thing either, but anyway, as long as the
source code is freely available, we can pull-in changes done for the Intland
clone. I wonder if there would be more active development on the
MercurialEclipse repository, if Andrei wouldn't have been hired by Intland,
as he was contributing before a lot. But in either case, the results of his
work are nice, I only hope they don't stick to that HgEclipse name.

Bastian


>
> /Zingo Andersen (Original author of mercurialeclipse but not so active
> anymore)
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20091216/4bb22d63/attachment.htm>