[core-workflow] Some questions

[Émanuel Barry]

Why thank you! I probably missed that last discussion.

 

Do you need some help? I can probably generate a file with that information and pass it over so you can check it matches the Mercurial one. I’m not used to dealing with the log graph though, but I can probably manage something. Here’s what I have in mind, let me know if you have another/better idea:

 

Take each X commit (say, every 100th or 1000th commit, or even every commit if we decide to be insane^Wprecise), store hashes of all files at that revision with possibly the file tree, in a .py file as a list or dict, or json or anything you prefer. Then I upload it for you to look at and you can compare with the mercurial repo. Or we run the same script on the mercurial repo and compare the resulting files.

 

I can work on that this week, probably. Sounds like a good idea?

-Emanuel

 

From: Senthil Kumaran [mailto:senthil at uthcode.com] 
Sent: Sunday, May 08, 2016 7:29 PM
To: Émanuel Barry
Cc: core-workflow
Subject: Re: [core-workflow] Some questions

 

 

On Sun, May 8, 2016 at 4:12 PM, Émanuel Barry <vgr255 at live.ca <mailto:vgr255 at live.ca> > wrote:

I understand that there's
already a semi-official mirror of the cpython repo on GitHub, and I've been
wondering why it isn't enough for our needs. 


It is suitable for our needs. Our last discussion was about how do we ascertain that

cpython git repo has the same history as the hg repo, so that after migrate we do not loose any information from the old system.

 

This could be done using:

 

* check the number of commits in both repos for each branch

* checking the hash of the source files in two repos.

* (And do we go about validating each piece of commit log graph too)?

 

If you have any suggestions, since you are using the cpython git mirror, please feel free to share your thoughts.

 

Welcome to the party!

 

Thanks,

Senthil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160508/7c376479/attachment.html>