Re: [sage-devel] Making libhomfly and libbraiding

2018-06-28 Thread Erik Bray
On Thu, Jun 28, 2018 at 5:30 PM mmarco wrote: > > Ok, let me know if you can verify that libbraiding works on cygwin. Done. Looks good to me! > El jueves, 28 de junio de 2018, 17:27:54 (UTC+2), Erik Bray escribió: >> >> On Thu, Jun 28, 2018 at 5:25 PM mmarco wrote: >> > >> > The packages libb

Re: [sage-devel] Re: Why my patch is not yet accepted?

2018-06-28 Thread Erik Bray
On Thu, Jun 28, 2018 at 12:55 AM Maarten Derickx wrote: > > Hi Victor, > > Just looked at the ticket, and without looking at the mathematical content I > see a few things that make the ticket probably not get attention from > reviewers. > > 1) The plugins of the patchbot currently show multiple

Re: [sage-devel] Sage Days about Python 3

2018-06-28 Thread Jeroen Demeyer
Given that many people cannot come, I decided to postpone this workshop to a different date. I haven't decided when, but I'm thinking october-november. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop recei

Re: [sage-devel] Making libhomfly and libbraiding

2018-06-28 Thread mmarco
Ok, let me know if you can verify that libbraiding works on cygwin. El jueves, 28 de junio de 2018, 17:27:54 (UTC+2), Erik Bray escribió: > > On Thu, Jun 28, 2018 at 5:25 PM mmarco > > wrote: > > > > The packages libbraiding and libhomfly have been optional for more than > a year. They provide

Re: [sage-devel] Making libhomfly and libbraiding

2018-06-28 Thread Erik Bray
On Thu, Jun 28, 2018 at 5:25 PM mmarco wrote: > > The packages libbraiding and libhomfly have been optional for more than a > year. They provide methods for braids and knots that many people find useful, > so I propose to make them standard packages. > > Are you ok with that? I need to test lib

[sage-devel] Making libhomfly and libbraiding

2018-06-28 Thread mmarco
The packages libbraiding and libhomfly have been optional for more than a year. They provide methods for braids and knots that many people find useful, so I propose to make them standard packages. Are you ok with that? -- You received this message because you are subscribed to the Google Group

Re: [sage-devel] Re: Deleting old upstream branches

2018-06-28 Thread Erik Bray
On Wed, Jun 27, 2018 at 8:11 PM Volker Braun wrote: > > I'm fine with auto-deleting merged branches, but IMHO thats just doctoring > around the symptoms. Listing all branches is just a fundamentally useless > view of the repo, akin to listing all your files alphabetically. Even if we > auto-del

[sage-devel] Re: Deleting old upstream branches

2018-06-28 Thread Ralf Stephan
On Wednesday, June 27, 2018 at 12:53:30 PM UTC+2, Erik Bray wrote: > > I did this just for myself and deleted ~205 branches. > ~127 here. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fr

[sage-devel] Re: Re: Deleting old upstream branches

2018-06-28 Thread Travis Scrimshaw
Should we also do this automatically for public/* branches? Or at least every stable/beta release? Best, Travis On Thursday, June 28, 2018 at 7:27:55 PM UTC+10, Marc Mezzarobba wrote: > > Erik Bray wrote: > > Personally I'm hesitant to touch that just because I don't want to go > > deleting *

[sage-devel] Re: Re: Deleting old upstream branches

2018-06-28 Thread Marc Mezzarobba
Erik Bray wrote: > Personally I'm hesitant to touch that just because I don't want to go > deleting *anyone*'s branches that aren't my own. FWIW, I've been deleting my old branches as well as some old public branches I had worked on for years now, and I don't think anyone ever complained. -- M