Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
"John D. Ament" <[email protected]> Sun, 09 Apr 2017 22:06:36 +0000
| Newsgroups | gmane.comp.apache.logging.log4cxx.devel,gmane.comp.apache.commons.general |
|---|---|
| Message-ID | <CAOqetn9q4qomBV6L5a4wB5n9KLEh4TSVWCCxUGJ7VRFnQBkpVw@mail.gmail.com> |
--001a114381ee1d27ed054cc31312 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 <[email protected]> wrote: > Thanks for the info Greg! > > Ralph > > > On Apr 6, 2017, at 9:14 PM, Greg Stein <[email protected]> wrote: > > > > On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Sch=C3=B6ning <tschoening@am-s= oft.de > <mailto:[email protected]>> 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 unti= l > you have everything you want in the resulting (local) git repository. Onc= e > 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 > > > > --001a114381ee1d27ed054cc31312 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Ralph,<div><br></div><div>It looks like most everything is= done.=C2=A0 If you don't get to it, I'll update the podlings.xml a= nd content/projects/log4cxx2.xml file to reflect graduation status.</div><d= iv><br></div><div>John<br><br><div class=3D"gmail_quote"><div dir=3D"ltr">O= n Fri, Apr 7, 2017 at 1:10 AM Ralph Goers <<a href=3D"mailto:ralph.goers= @dslextreme.com">[email protected]</a>> wrote:<br></div><blockq= uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc = solid;padding-left:1ex">Thanks for the info Greg!<br class=3D"gmail_msg"> <br class=3D"gmail_msg"> Ralph<br class=3D"gmail_msg"> <br class=3D"gmail_msg"> > On Apr 6, 2017, at 9:14 PM, Greg Stein <<a href=3D"mailto:gstein@gm= ail.com" class=3D"gmail_msg" target=3D"_blank">[email protected]</a>> wro= te:<br class=3D"gmail_msg"> ><br class=3D"gmail_msg"> > On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Sch=C3=B6ning <<a href=3D"= mailto:[email protected]" class=3D"gmail_msg" target=3D"_blank">tschoen= [email protected]</a> <mailto:<a href=3D"mailto:[email protected]" clas= s=3D"gmail_msg" target=3D"_blank">[email protected]</a>>> wrote:<= br class=3D"gmail_msg"> > >...<br class=3D"gmail_msg"> > > and I am not quite sure what the process is to move<br class=3D"g= mail_msg"> > > from svn to git without losing history.=C2=A0 I guess I will just= create<br class=3D"gmail_msg"> > > a Jira issue for infra and find out.<br class=3D"gmail_msg"> ><br class=3D"gmail_msg"> > From my understanding, a logging PMC needs to create the GIT repo:<br = class=3D"gmail_msg"> ><br class=3D"gmail_msg"> > Yeup.<br class=3D"gmail_msg"> ><br class=3D"gmail_msg"> > >...<br class=3D"gmail_msg"> > Additionally, the current SVN repo needs to be imported into a local<b= r class=3D"gmail_msg"> > GIT repo and that import can than be pushed to the newly created at<br= class=3D"gmail_msg"> > Apache. Not sure where the SVN repo goes afterwards...<br class=3D"gma= il_msg"> ><br class=3D"gmail_msg"> > The svn repo sticks around, and we just switch it to read-only (file a= n INFRA ticket when ready for that).<br class=3D"gmail_msg"> ><br class=3D"gmail_msg"> > In some former Mail, Matt thankfully offered to do the repo creation<b= r class=3D"gmail_msg"> > and GIT import, but at least the import is something I could have a<br= class=3D"gmail_msg"> > look at myself as well. Shouldn't make any difference who pushes t= he<br class=3D"gmail_msg"> > history in the end.<br class=3D"gmail_msg"> ><br class=3D"gmail_msg"> > Yes. The Logging community can run svn2git and tweak its operation unt= il you have everything you want in the resulting (local) git repository. On= ce 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 durin= g that push)<br class=3D"gmail_msg"> ><br class=3D"gmail_msg"> > Cheers,<br class=3D"gmail_msg"> > Greg Stein<br class=3D"gmail_msg"> > Infrastructure Administrator, ASF<br class=3D"gmail_msg"> ><br class=3D"gmail_msg"> <br class=3D"gmail_msg"> </blockquote></div></div></div> --001a114381ee1d27ed054cc31312--