[mkroot] Project rename.

Rob Landley rob at landley.net
Fri Mar 16 09:31:54 PDT 2018


The problem with renaming the github is it's not obvious where to find the new
one (the old one's just a 404). So I think what I should do is:

1) Cut a release under the current name, but announce the project will rename
_next_ release.

2) Leave the mailing list under the current name, with the current archive
repository URL.

That sound like a reasonable approach? (This has been holding up the release
because I didn't know whether I should do the release under the new name or the
old name...)

Rob


More information about the mkroot mailing list