On Wednesday, June 14, 2023 at 5:08:11 PM UTC-7 Dima Pasechnik wrote:
On Wed, Jun 14, 2023 at 7:11 PM Matthias Koeppe
wrote:
>
> We did have sagemath/sage with branches develop and master.
> And you made releases there.
so it wasn't a good idea to rename/duplicate it.
Well, it was the o
On Wed, Jun 14, 2023 at 7:11 PM Matthias Koeppe
wrote:
>
> We did have sagemath/sage with branches develop and master.
> And you made releases there.
well, it's to understand how exactly Zenodo integration broke.
Apparently for them renaming of a repo is not a reason to turn the
integration off,
We did have sagemath/sage with branches develop and master.
And you made releases there.
On Wednesday, June 14, 2023 at 10:59:57 AM UTC-7 Dima Pasechnik wrote:
>
>
> On Wed, 14 Jun 2023, 18:52 Matthias Koeppe, wrote:
>
>> On Wednesday, June 14, 2023 at 10:49:14 AM UTC-7 Dima Pasechnik wrote:
>>
On Wed, 14 Jun 2023, 18:52 Matthias Koeppe,
wrote:
> On Wednesday, June 14, 2023 at 10:49:14 AM UTC-7 Dima Pasechnik wrote:
>
> I also don't understand why sage-archive-2023-02-01 repo has releases.
> Was this repo created by some kind of a GitHub-specific clonig process?
>
>
> As it says in its
On Wednesday, June 14, 2023 at 10:49:14 AM UTC-7 Dima Pasechnik wrote:
I also don't understand why sage-archive-2023-02-01 repo has releases.
Was this repo created by some kind of a GitHub-specific clonig process?
As it says in its "About" box: "This repository used to be the user-facing
mirro
