Email list hosting service & mailing list manager

SRFI development in the age of git John Cowan (12 Jul 2020 23:15 UTC)
Re: SRFI development in the age of git Bradley Lucier (12 Jul 2020 23:54 UTC)
Re: SRFI development in the age of git Arthur A. Gleckler (13 Jul 2020 00:31 UTC)
Re: SRFI development in the age of git Arthur A. Gleckler (13 Jul 2020 00:30 UTC)
Re: SRFI development in the age of git Arthur A. Gleckler (13 Jul 2020 01:35 UTC)
Re: SRFI development in the age of git Marc Nieper-Wißkirchen (13 Jul 2020 06:45 UTC)
Re: SRFI development in the age of git Linas Vepstas (13 Jul 2020 07:05 UTC)
Re: SRFI development in the age of git Marc Nieper-Wißkirchen (13 Jul 2020 07:09 UTC)
Re: SRFI development in the age of git Linas Vepstas (13 Jul 2020 07:34 UTC)
Re: SRFI development in the age of git John Cowan (13 Jul 2020 18:10 UTC)
Re: SRFI development in the age of git Linas Vepstas (13 Jul 2020 21:40 UTC)
Re: SRFI development in the age of git John Cowan (14 Jul 2020 00:38 UTC)
Re: SRFI development in the age of git Marc Nieper-Wißkirchen (14 Jul 2020 09:59 UTC)
Re: SRFI development in the age of git Linas Vepstas (14 Jul 2020 22:54 UTC)
Re: SRFI development in the age of git John Cowan (14 Jul 2020 23:12 UTC)
Re: SRFI development in the age of git Linas Vepstas (14 Jul 2020 23:57 UTC)
Re: SRFI development in the age of git John Cowan (15 Jul 2020 03:51 UTC)
Re: SRFI development in the age of git Linas Vepstas (15 Jul 2020 08:34 UTC)
Re: SRFI development in the age of git Arthur A. Gleckler (13 Jul 2020 07:40 UTC)
Re: SRFI development in the age of git Marc Nieper-Wißkirchen (13 Jul 2020 07:46 UTC)
Re: SRFI development in the age of git Arthur A. Gleckler (13 Jul 2020 15:59 UTC)

Re: SRFI development in the age of git Marc Nieper-Wißkirchen 13 Jul 2020 07:09 UTC

Am Mo., 13. Juli 2020 um 09:05 Uhr schrieb Linas Vepstas
<xxxxxx@gmail.com>:
>
> On Mon, Jul 13, 2020 at 1:45 AM Marc Nieper-Wißkirchen <xxxxxx@nieper-wisskirchen.de> wrote:
>>
>> Couldn't all the author's and editor's draft happen in the central
>> repository as well? Git has branches, so it is easy to have an
>> author's branch. As everything will just have one history, it will
>> make things easier for reviewers and testers.
>
>
> In github, it is easy to see other repos, as well. Just click on "insights" and then click on "network"  or something like that, it shows every fork, every branch in every fork. in a nice graphical diagram.  I'd quote the URL except that github seems to be "500 server error" just right now.

We shouldn't rely on Github-only functionality. It's a proprietary
platform, which is not under our command. I would prefer to use
Git-only features.