On 2017-12-23, Dinesh Thirumurthy <dinesh.thirumur...@gmail.com> wrote:
> Stephan,
>
> Thank you.
>
>> Note that openbsd's github conversion is not considered stable yet.
>
> I was using github.com because it is (ahem) more palatable. :-)
> So, it should be a hit with students.
>
>> Which means all commit hashes could change at any time. Regardless
>> of the crypto export issue, I would not rely on it for very important
>> tasks until it is declared stable.
>
> Okay. I fine with that.
>
>> If you really want it in git format without legal trouble, you could
>> create your own git conversion with e.g. git-cvs ('pkg_add git-cvs').
>
> Thanks very much. I was trying to get in touch with Bob Beck to figure
> this out.
>
> Regards,
> Dinsh
>
>
>
The conversion on github is done with cvs2gitdump. After testing all of
the conversion tools I could find, this was the one which had the fewest
problems with OpenBSD's slightly broken rcs files. (In particular,
anything which tries to convert branches is very likely to break).
For git-cvs here's a snip from the mail I wrote Uwe back in 2015:
<< When an update is committed to a file that was previously imported,
the import is shown again in "git log". It looks like it happens for the
first commit after import. >>
