Email list hosting service & mailing list manager

Re: R7RS Large moving from Bitbucket to Github Lassi Kortela (27 Jun 2020 20:11 UTC)
Re: R7RS Large moving from Bitbucket to Github John Cowan (27 Jun 2020 20:53 UTC)
Re: R7RS Large moving from Bitbucket to Github Lassi Kortela (28 Jun 2020 17:25 UTC)

Re: R7RS Large moving from Bitbucket to Github Lassi Kortela 28 Jun 2020 17:25 UTC

>     The following three repos exist under John's GitHub account:
>
>     * https://github.com/johnwcowan/r7rs
>
> That was empty and I deleted it.
>
>     * https://github.com/johnwcowan/r7rs-work
>
> This is much of the history of the project, including all the pre-SRFIs
> I've developed and some bits and pieces of code.
>
>     * https://github.com/johnwcowan/r7rs-spec
>
>     Does today's announcement imply that w7rs-spec will be the only one of
>     the three that will stay relevant going forward?
>
>   r7rs-work will be relevant until R7RS-large is over, and even then it
> will contain the history (along with small.r7rs.org
> <http://small.r7rs.org>) and be a source of ideas.

Thanks. So r7rs-spec currently covers the r7rs-small TeX sources. Will
it be extended to cover r7rs-large in the future?

r7rs-work is for drafts. Makes sense.

The default branch in both repos is idiosyncratic; it's not clear which
branch we should follow. Is there an easy way to transition the repos so
that the workflow is centered around 'master' as is usual for git? If
memory serves, these originated as Mercurial repos and the current
branch arrangements are caused by that.