Migration to GitHub complete

145 views
Skip to first unread message

Matthias Koeppe

unread,
Feb 6, 2023, 2:02:59 AM2/6/23
to sage-devel

Kwankyu Lee

unread,
Feb 6, 2023, 2:20:58 AM2/6/23
to sage-devel
Great! Thank you!

G. M.-S.

unread,
Feb 6, 2023, 2:25:30 AM2/6/23
to sage-...@googlegroups.com

Huge thanks to everybody involved.

Guillermo

Marc Mezzarobba

unread,
Feb 6, 2023, 4:07:02 AM2/6/23
to sage-...@googlegroups.com
Thank you all for your work!

A minor point: the PR template still says "we are not accepting pull
requests yet".

--
Marc

Eric Gourgoulhon

unread,
Feb 6, 2023, 4:17:56 AM2/6/23
to sage-devel
Le lundi 6 février 2023 à 08:25:30 UTC+1, GMS a écrit :

Huge thanks to everybody involved.

+1 

Eric.  

Marc Mezzarobba

unread,
Feb 6, 2023, 4:31:25 AM2/6/23
to sage-...@googlegroups.com
Marc Mezzarobba wrote:
> A minor point: the PR template still says "we are not accepting pull
> requests yet".

Another one (more of a warning to other users actually): apparently
subscriptions to issues have not been migrated; you need to
re-subscribe to issues you are interested in.

--
Marc

Dima Pasechnik

unread,
Feb 6, 2023, 5:27:50 AM2/6/23
to sage-...@googlegroups.com
I've just fixed this one. We still need to create a real tempate...
>
> --
> Marc
>
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/trqfvc%2473j%241%40ciao.gmane.io.

Emmanuel Charpentier

unread,
Feb 6, 2023, 9:45:12 AM2/6/23
to sage-devel
After followong the steps given for an existing tree, my develop branch still followed OLD-ORIGIN. Shouldn't that be orign ?

Kwankyu Lee

unread,
Feb 6, 2023, 9:51:43 AM2/6/23
to sage-devel
On Monday, February 6, 2023 at 11:45:12 PM UTC+9 emanuel.c...@gmail.com wrote:
After followong the steps given for an existing tree, my develop branch still followed OLD-ORIGIN. Shouldn't that be orign ?

You remove the develop branch, and make a new one (named develop) from the remote origin. 

Kwankyu Lee

unread,
Feb 6, 2023, 10:03:39 AM2/6/23
to sage-devel
No. Make it from the remote upstream, so I think the command is 

git branch -D develop; g checkout -b develop upstream/develop

Kwankyu Lee

unread,
Feb 6, 2023, 10:06:34 AM2/6/23
to sage-devel
Or 

git branch -D develop; git branch --track develop upstream/develop 

Marc Mezzarobba

unread,
Feb 6, 2023, 12:41:14 PM2/6/23
to sage-...@googlegroups.com
Marc Mezzarobba wrote:
> Another one (more of a warning to other users actually): apparently
> subscriptions to issues have not been migrated; you need to
> re-subscribe to issues you are interested in.

Maybe related: search patterns of the form mentions:someone (including
the default filter 'Everything mentioning you') seem to only return
issues created after the migration. ('author:someone' works fine.)

--
Marc

Marc Mezzarobba

unread,
Feb 6, 2023, 12:57:40 PM2/6/23
to sage-...@googlegroups.com
Marc Mezzarobba wrote:
> Maybe related: search patterns of the form mentions:someone (including
> the default filter 'Everything mentioning you') seem to only return
> issues created after the migration.

...However, involves:@me seems to work.

--
Marc

Matthias Koeppe

unread,
Feb 6, 2023, 2:22:13 PM2/6/23
to sage-devel

Emmanuel Charpentier

unread,
Feb 6, 2023, 3:42:52 PM2/6/23
to sage-devel
Thank you !

But I already restarted in a fresh tree, which gad the unexpected side effect of seriously deflating its size (9,4 GB vs 24 GB in the old tree...).

The migration guide should be amended...

kcrisman

unread,
Feb 6, 2023, 9:40:36 PM2/6/23
to sage-devel
Gratuliere and congratulations to all the many people who made this huge task possible! 
Reply all
Reply to author
Forward
0 new messages