I went ahead and placed my updates for the OSGi R7 resolver v1.1 specification in osgi-r7/resolver. Thanks for the tip on svn cp.
Tom On Thu, Jan 5, 2017 at 10:46 AM, Carsten Ziegeler <[email protected]> wrote: > Thomas Watson wrote > > I'm fine with this approach, but I do wonder what the history of the > files > > will look like after all this copying around of source code. It would be > > nice if the history of the files contained in the release folders (i.e. > > trunk/scr) maintained the proper history so we can lookup what revision > > changed a line of code etc. > > > > The history looks good as I used svn cp, so all is preservered > > Regards > Carsten > > > Tom > > > > On Thu, Jan 5, 2017 at 10:19 AM, Carsten Ziegeler <[email protected]> > > wrote: > > > >> Felix Meschberger wrote > >>> > >>>> > >>>> What about renaming scr to scr-r7-branch and scr-2.0.x to scr and the > >>>> same for config admin but leaving them in trunk? > >>>> Or creating and osgi-r7 directory in trunk and move the stuff there? > >>> > >>> I like the folder, because it then properly delineates all the OSGI R7 > >> work. > >>> > >> > >> Ok, I'll let this settle some days to give everyone a chance to complain > >> upfront. > >> If no one comes up with a better proposal, I'll go ahead and do the > >> changes. > >> > >> Regards > >> > >> Carsten > >> > >> -- > >> Carsten Ziegeler > >> Adobe Research Switzerland > >> [email protected] > >> > > > > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected] >
