Yes, please go ahead. Ralph
> On Apr 9, 2017, at 3:06 PM, John D. Ament <johndam...@apache.org> wrote: > > Ralph, > > It looks like most everything is done. If you don't get to it, I'll update > the podlings.xml and content/projects/log4cxx2.xml file to reflect graduation > status. > > John > > On Fri, Apr 7, 2017 at 1:10 AM Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Thanks for the info Greg! > > Ralph > > > On Apr 6, 2017, at 9:14 PM, Greg Stein <gst...@gmail.com > > <mailto:gst...@gmail.com>> wrote: > > > > On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <tschoen...@am-soft.de > > <mailto:tschoen...@am-soft.de> <mailto:tschoen...@am-soft.de > > <mailto:tschoen...@am-soft.de>>> wrote: > > >... > > > and I am not quite sure what the process is to move > > > from svn to git without losing history. I guess I will just create > > > a Jira issue for infra and find out. > > > > From my understanding, a logging PMC needs to create the GIT repo: > > > > Yeup. > > > > >... > > Additionally, the current SVN repo needs to be imported into a local > > GIT repo and that import can than be pushed to the newly created at > > Apache. Not sure where the SVN repo goes afterwards... > > > > The svn repo sticks around, and we just switch it to read-only (file an > > INFRA ticket when ready for that). > > > > In some former Mail, Matt thankfully offered to do the repo creation > > and GIT import, but at least the import is something I could have a > > look at myself as well. Shouldn't make any difference who pushes the > > history in the end. > > > > Yes. The Logging community can run svn2git and tweak its operation until > > you have everything you want in the resulting (local) git repository. Once > > it all looks good, then push all of that history into the newly-created > > git-wip repository. (you may want to have INFRA disable commit emails > > during that push) > > > > Cheers, > > Greg Stein > > Infrastructure Administrator, ASF > > >
