Well, my two cents is indeed to do things by the book in GitHub-land for the reasons that you mentioned (e.g., forks are still linked, etc.) But perhaps if that's going to be a protracted or painful process, it's worth reconsidering.
On Tue, Sep 27, 2016 at 4:54 PM, Daniel Beck <[email protected]> wrote: > > > On 27.09.2016, at 22:09, Ben Patterson <[email protected]> wrote: > > > > It sounds good to me. FWIW I had submitted an issue to the 'current' > parent repo; I assume GH would only make the switch if all parties agree. > > Breaking the connection shouldn't need that -- we could delete the repo, > create a new one, then push --mirror to get a similar effect. > > That said, maybe inverting the link, making jenkinci's the root of the > network, would be preferable? Otherwise it's disconnected from all existing > forks. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jenkinsci-dev/iHBzu1sBOmI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/9CCB5398-6D4E-4C60-AC9D-48604129CE27%40beckweb.net. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAAT-2mVpnFVjnutrk1%2Bpw%2Bxa7SmzEDpj0J1FUwmA%3DCvkoYx7gw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
