Yeah this repo in theory is done after 1.6.7, so I think we can rename it or something to not confuse people once we put 1.6.7 out. We should probably keep it either as a branch or a renamed repo for posterity.
-Tom On Fri, Feb 17, 2012 at 7:32 PM, Charles Oliver Nutter <head...@headius.com> wrote: > Perhaps we can take that and make it a branch of the original...or > not. Doesn't matter much to me...the jnr repo is the canonical one, so > this is just slowly fading now. > > - Charlie > > On Fri, Feb 17, 2012 at 3:56 PM, Thomas E Enebo <tom.en...@gmail.com> wrote: >> It is still the repo for all JRuby 1.6.x builds. >> >> -Tom >> >> On Fri, Feb 17, 2012 at 3:42 PM, Charles Oliver Nutter >> <head...@headius.com> wrote: >>> Could be...I am not sure if we use it anymore. Tom? >>> >>> On Feb 17, 2012 10:31 AM, "Nick Sieger" <nicksie...@gmail.com> wrote: >>>> >>>> Looks like jnr-posix is the only other repo under the jruby org that fits >>>> this description. Should it just be deleted? >>>> >>>> /Nick >>>> >>>> On Feb 17, 2012, at 3:43 AM, Charles Oliver Nutter wrote: >>>> >>>> > I found a simple reason why it's better to duplicate a repo when >>>> > moving it into an organization: pull requests go there. If you fork a >>>> > repository, as we did from vvs/jruby-launcher to jruby/jruby-launcher, >>>> > then forks of your fork will try to send pull requests back to the >>>> > originating repository. >>>> > >>>> > In this case, since vvs/jruby-launcher is no longer the canonical >>>> > repository for jruby-launcher, I deleted it and recreated it with the >>>> > same repo, rather than using github forking. >>>> > >>>> > I recommend we do this for any projects that have their canonical >>>> > source in the 'jruby' organization on Github but are currently "forks" >>>> > of some other repository, so that pull requests go to the right place. >>>> > >>>> > - Charlie >>>> > >>>> > --------------------------------------------------------------------- >>>> > To unsubscribe from this list, please visit: >>>> > >>>> > http://xircles.codehaus.org/manage_email >>>> > >>>> > >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >> >> >> >> -- >> blog: http://blog.enebo.com twitter: tom_enebo >> mail: tom.en...@gmail.com >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- blog: http://blog.enebo.com twitter: tom_enebo mail: tom.en...@gmail.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
