Here's an argument from a different perspective. It's easy to inter-operate
with GIT from HG:
http://hg-git.github.com/
<http://hg-git.github.com/>It's more difficult to do it the other way
around. To work with HG from GIT involves hg-git as well, but you need to
import/export to Git at the command line instead of just using the standard
pull/push commands. Basically, the barrier is higher.
So, if Git is selected, people can use either client fairly easily. Note
that hg-git is lossless and was created by the folks at GitHub.
Patrick Earl
On Wed, Nov 3, 2010 at 6:00 AM, Patrick Earl <[email protected]> wrote:
> While I originally preferred Mercurial, I've changed my view, and now use
> GIT, for these reasons:
>
> 1. Though subjective, Git still seems to be more powerful and popular.
> 2. Castle selected Git.
> 3. Mono selected Git.
> 4. There is NGit, an active .NET implementation of Git.
> 5. The windows support is fine in TortoiseGIT (just like TortoiseSVN).
> While I do on occasion have to run a command at the command line, routine
> operations work well from the Tortoise GUI, just like TortoiseSVN.
> 6. Git tends to be supported first in places like continous integration
> servers.
> 7. While these last two points may mean nothing in this context, here they
> are anyways... we found it easier to "sell" Git to a major client because of
> the broad recognition. We are a .NET shop and ended up selecting Git as our
> internal VCS.
>
> Patrick Earl
>
> On Wed, Nov 3, 2010 at 4:30 AM, Fabio Maulo <[email protected]> wrote:
>
>> If you don't have problem I would use Mercurial; Can I ?
>>
>> --
>> Fabio Maulo
>>
>>
>> El 02/11/2010, a las 16:38, Jorge <[email protected]> escribió:
>>
>> > Hello there,
>> >
>> > I am in the process of downloading the code via SVN, and it is taking
>> > a very long time.
>> >
>> > Can someone please enable Git repo in sourceforge, or better yet, move
>> > code to Github?
>> >
>> > Respectfully yours,
>> > Jorge
>>
>
>
