Well for the record I started with mercurial and I'm now using git ;)

You would have to sync the repos "by hand" then, right ? Also it may be 
better to have a central place for bug reports, it would be confusing to 
have a list on bitbucket and a list on github (not mentioning the google 
code archive)...

Le mercredi 13 novembre 2013 16:08:47 UTC+1, Carlos Córdoba a écrit :
>
>  Exactly, that's what I'm planning to do: use hg-git to maintain a mirror 
> on Github while leaving our main repo on Bitbucket.
>
> El 13/11/13 10:05, Matt Anderson escribió:
>  
> I do a lot of work in Mercurial and prefer it, but I think it is mostly a 
> matter of which dcvs you started with.  When I have to contribute code with 
> die hard git folks (which it turns out are all git folks) I have used 
> http://hg-git.github.io/.  It works amazingly well at pushing to git 
> repos and pulling them back to your computer as an hg repo.  Anyone who was 
> so inclined could easily use it to mirror a mercurial database to github
>
>
> On Wed, Nov 13, 2013 at 8:44 AM, Carlos Córdoba 
> <[email protected]<javascript:>
> > wrote:
>
>>  Hi Joseph,
>>
>> Thanks for putting the issue forward. I think we really need to move, 
>> either to Github or Bitbucket because GoogleCode is quite limited, and 
>> there is an increased interest on new contributions.
>>
>> The easiest path for now is just to move to BitBucket. As I said in Issue 
>> 816, I love Mercurial and TortoiseHg and I'm very comfortable with both; in 
>> contrast git seems too command line oriented. Pierre also mentioned a while 
>> back that he doesn't have time to learn a new VCS, and since he is still by 
>> far our largest contributor and the man behind the great design that 
>> supports Spyder, I wouldn't like to leave him out. Besides Bitbucket is not 
>> that far away of GitHub feature-wise, and this will be far less disruptive 
>> until we finish 2.3.
>>
>> I think it won't be that hard to create a read/write mirror on Github for 
>> people who wants to send their pull requests through it, which I plan to 
>> investigate after 2.3. That way we could have both worlds at once without 
>> too many problems.
>>
>> Cheers,
>> Carlos
>>
>> El 13/11/13 08:53, Joseph Martinot-Lagarde escribió:
>>   
>> The discussion on 
>> https://groups.google.com/forum/#!topic/spyderlib/5tw2ZItlxUM remind me 
>> of http://code.google.com/p/spyderlib/issues/detail?id=816.
>> Google code clearly lacks functionalities compared to Bitbucket and 
>> Github (the main one being pull requests, I think). In addition to this is 
>> the eventuality to shift to git instead of mercurial.
>>
>> Disclaimer: I'm currently a git user so I'm biased and I don't know 
>> mercurial very well
>>
>> From the tip of my head, here are the pros and cons I can find for each 
>> service :
>>
>>
>> *Bitbucket/Mercurial *+ Uses mercurial and git. This allows to keep 
>> mercurial as VCS.
>> + TortoiseHg
>> - less users
>>
>>
>> * Github/Git *- Git only
>> + numpy, scipy, ipython and matplotlib use it
>> + more users
>> - tracker data has a proprietary format (but is it important ?)
>>
>> There is also the possibility to have read/write mirror I guess, but I 
>> have no clue of how it works...
>>
>> Why I prefer Git over Mercurial :
>> + 2-stage commits helps to check the correctness of commits
>> + easy selection line by line or block by block instead of whole files 
>> for commits (using git gui)
>> + git stash
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "spyder" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected]<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/spyderlib.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>    -- 
>> You received this message because you are subscribed to the Google Groups 
>> "spyder" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected]<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/spyderlib.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>  
>  -- 
> You received this message because you are subscribed to the Google Groups 
> "spyder" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To post to this group, send email to [email protected]<javascript:>
> .
> Visit this group at http://groups.google.com/group/spyderlib.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> 

-- 
You received this message because you are subscribed to the Google Groups 
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to