Didn't we have that problem previously that OS updates would overwrite system config (I'm guessing thats what happened).
On Monday, September 26, 2016 at 12:02:36 PM UTC+2, Dima Pasechnik wrote: > > > > On Monday, September 26, 2016 at 9:04:08 AM UTC, Volker Braun wrote: >> >> Somebody killed unauthorized git:// over the weekend... incorrect >> firewall rule? >> > > It was William, I suppose. > Actually, disabling anonymous git:// would perhaps help to reduce server > load, without > real functionality problems for development... > > >> >> On Monday, September 26, 2016 at 10:52:13 AM UTC+2, Harald Schilly wrote: >>> >>> On Mon, Sep 26, 2016 at 10:16 AM, Dima Pasechnik <dim...@gmail.com> >>> wrote: >>> > this really has to be documented properly. >>> >>> just added to your ticket a comment, repeating it here: >>> it's not only the git-trac page, but also the "the hard way" page: >>> http://doc.sagemath.org/html/en/developer/manual_git.html#the-trac-server >>> where git:// is mentioned. >>> it's probably best to condense all this down to a single minimal case >>> that covers the full development setup with ssh keys. >>> >>> -- h >>> >> -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.