Message13114

My second attempt at this (or the 20th, depending how you count) is at https://github.com/jeff5/jython-whinchat and does not have the history problem Jim detected. I would be grateful to as many people as can check my work.

Now I seem to have produced a correct result, subject to confirmation, I'm going to ask GitHub support how we might best replace jython/jython with repo content produced by an identical process. This will also make them aware of the failings of their tool.

There are some gains from having to do this again: I'm much better acquainted with the history, I was also able to fix other niggles (like a change of my own I mis-attributed), and I was able to minimise the number of tags lost with change sets at unnamed heads. It's some compensation for GitHub eating my week-end.