Now that I'm comfortable declaring the code for the CLA bot finished (
https://github.com/python/the-knights-who-say-ni), the next step is to
finalize the command(s) we are going to use to convert hg repositories to
git for migration to GitHub. Senthil, are you ready to make a final
decision?
Once
I had initially suggested hg-git, but after my (mostly negative) experience
in trying to convert the CPython repo, my vote goes towards fast-export.
Partly because it's the only once *specifically* designed for exporting,
not trying to be a bridge like hg-git and the other tool.
--
Ryan
[ERROR]: Y
Hi Brett,
On Fri, Apr 22, 2016 at 4:27 PM, Brett Cannon wrote:
> Now that I'm comfortable declaring the code for the CLA bot finished (
> https://github.com/python/the-knights-who-say-ni), the next step is to
> finalize the command(s) we are going to use to convert hg repositories to
> git for m
On Fri, Apr 22, 2016, 18:45 Senthil Kumaran wrote:
> Hi Brett,
>
> On Fri, Apr 22, 2016 at 4:27 PM, Brett Cannon wrote:
>
>> Now that I'm comfortable declaring the code for the CLA bot finished (
>> https://github.com/python/the-knights-who-say-ni), the next step is to
>> finalize the command(s)
By way of Twitter, I came across
https://github.com/nayafia/contributing-template/blob/master/CONTRIBUTING-template.md
today, and it made me realise something: we should probably add reviewing
and potentially updating the README as part of the GitHub migration.
The reason I suggest that is that wi
2016-04-22 22:45 GMT-03:00 Senthil Kumaran :
> Hi Brett,
>
> On Fri, Apr 22, 2016 at 4:27 PM, Brett Cannon wrote:
>>
>> Now that I'm comfortable declaring the code for the CLA bot finished
>> (https://github.com/python/the-knights-who-say-ni), the next step is to
>> finalize the command(s) we are
On Fri, Apr 22, 2016 at 11:40 PM Nick Coghlan wrote:
> The reason I suggest that is that with the way code hosting services like
> GitHub work, the README changes from something people may read for local
> development after they've already cloned the repo to instead being the main
> landing page
