Just write to support, they react really fast and solve issues. > On Oct 3, 2016, at 14:57, Baptiste Mathus <[email protected]> wrote: > > Maybe GitHub could just set up the link on existing repos to [conceptually] > forked ones? I've asked them on Twitter to see if they have an answer. Might > be possible, since the contrary is and we regularly ask them to "break" fork > links. > > 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou <[email protected] > <mailto:[email protected]>>: > +1 Url in top of page should be enough imho. > Maybe name repository `xstream-jenkins` as project do `-jenkins` releases? > > On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote: > I've created https://github.com/jenkinsci/xstream-fork > <https://github.com/jenkinsci/xstream-fork>, branch "jenkins" is based on > upstream tag 1.4.7 + diff from our fork, so code is equivalent to > https://github.com/jenkinsci/xstream <https://github.com/jenkinsci/xstream> > > Are you OK I documented on jenkinsci/xstream this repo is deprecated and > redirect users to jenkinsci/xstream-fork if they want to propose PRs ? > > > 2016-09-30 23:35 GMT+02:00 Mark Waite <[email protected] <>>: > Wouldn't it be better to leave the existing repository with its current name > to prevent breaking anyone who depends on that location, then create the > forked repository under an entirely new name (like xstream-fork)? > > Other than that minor item, I think it is an interesting idea to clearly show > projects which are forks of an upstream project. > > Mark Waite > > On Fri, Sep 30, 2016 at 2:32 PM nicolas de loof <[email protected] <>> > wrote: > Hi, > > Jenkins uses some custom builds of external libraries, typically XStream. > Today such projects are hosted on github, which would make easier to keep in > sync and/or propose fixes to upstream project. But we can't reconcile > existing repository with project's github. > > Typical sample : > https://github.com/jenkinsci/xstream/ <https://github.com/jenkinsci/xstream/> > vs https://github.com/x-stream/xstream <https://github.com/x-stream/xstream> > > I suggest we rename such a repo on jenkinsci organization as "-legacy", then > fork the upstream project, and apply a diff to ensure we get our own changes > back (or maybe try to cherry-pick patches, which would be nicer but more > complex). > > We could then ensure PR made to jenkinsci are also proposed to upstream > project and we only include fixes that are strictly related to jenkins usage, > or at least changes we approved might be included in a future upstream > project release > > wdyt ? > > > > -- > 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/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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/CAO49JtGPpRL%3Dh0kHeQ2Lh4isi6eNrboSZYhzRMdx9PRm%2Bghz6A%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGPpRL%3Dh0kHeQ2Lh4isi6eNrboSZYhzRMdx9PRm%2Bghz6A%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/4feee351-d040-4782-8876-a90034266d12%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/4feee351-d040-4782-8876-a90034266d12%40googlegroups.com?utm_medium=email&utm_source=footer>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > 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/nZvl6Ra3P-M/unsubscribe > <https://groups.google.com/d/topic/jenkinsci-dev/nZvl6Ra3P-M/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5Yas1u4WU8wPRNnNr9vG-QX8J-DT-K8TqmQo2gGbyc3Q%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5Yas1u4WU8wPRNnNr9vG-QX8J-DT-K8TqmQo2gGbyc3Q%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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/E08ED313-ECA5-4720-97A5-5B8DF17EFC22%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
