Re: Before declaring Bochs is dead ...
Colin Nichols <[email protected]> Wed, 13 Jul 2022 14:04:56 -0400
| Newsgroups | gmane.comp.emulators.bochs.devel |
|---|---|
| Message-ID | <CAA1d=ETuudrPV-T-k2PHNdoscrBud=4mvnS4gSPqcmjvo9COKg@mail.gmail.com> |
--===============6722076483361673715== Content-Type: multipart/alternative; boundary="0000000000000913e305e3b3a0d9" --0000000000000913e305e3b3a0d9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Done - https://github.com/stlintel/Bochs/pull/1 On Wed, Jul 13, 2022 at 12:41 PM <[email protected]> wrote: > Please submit a pull request. Want to see how it looks like. > > Content doesn=E2=80=99t matter =E2=80=93 adding README is good. > > > > *From:* Colin Nichols <[email protected]> > *Sent:* Wednesday, 13 July 2022 15:20 > *To:* Saulius Krasuckas <[email protected]> > *Cc:* Stanislav <[email protected]>; bochs-developers < > [email protected]> > *Subject:* Re: [Bochs-developers] Before declaring Bochs is dead ... > > > > Hello, I'm very excited to see Bochs moving to Github! > > > > I'd like to add a README.md to make the repo page a bit less bare. Maybe > this would be a good first PR to test out the workflow? > > > > For now, I'll mostly link into SF for e.g. documentation. For > bugs/managing development - is the intention to use Github issues going > forward? I would be in favor of this (said as someone who has not > contributed code... yet) > > > > > Can someone help with setting up mandatory code review for pull > > requests ? > > I can help with this if you'd like > > > > > > Thank you > > Colin > > > > > > On Mon, Jul 11, 2022 at 1:57 PM Saulius Krasuckas <[email protected]> > wrote: > > On 2022-07-11 09:26, [email protected] wrote: > > > Please take a look onto github repository: > > https://github.com/stlintel/Bochs > > and also SF git repository: > > https://sourceforge.net/p/bochs/bochs/ci/master/tree/ > > Thanks! > > > I personally prefer github interface. > > Me too. I already starred, forked the repo here, and turned on watching > (following) it. > > > Can someone help with setting up mandatory code review for pull > > requests ? > > Not this time. But maybe this paragraph or even whole article could > give some insight: > https://github.blog/2018-03-23-require-multiple-reviewers/#how-it-works > > S. > > > _______________________________________________ > bochs-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bochs-developers > > --0000000000000913e305e3b3a0d9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Done -=C2=A0<a href=3D"https://github.com/stlintel/Bochs/p= ull/1">https://github.com/stlintel/Bochs/pull/1</a><br></div><br><div class= =3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 13, 2022= at 12:41 PM <<a href=3D"mailto:[email protected]">[email protected]</= a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p= x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d= iv lang=3D"en-IL" style=3D"overflow-wrap: break-word;"><div class=3D"gmail-= m_-4926276770797164940WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN= -US">Please submit a pull request. Want to see how it looks like.<u></u><u>= </u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Content doesn=E2= =80=99t matter =E2=80=93 adding README is good.<u></u><u></u></span></p><p = class=3D"MsoNormal"><span lang=3D"en-IL"><u></u>=C2=A0<u></u></span></p><di= v style=3D"border-right:none;border-bottom:none;border-left:none;border-top= :1pt solid rgb(225,225,225);padding:3pt 0cm 0cm"><p class=3D"MsoNormal"><b>= <span lang=3D"EN-US">From:</span></b><span lang=3D"EN-US"> Colin Nichols &l= t;<a href=3D"mailto:[email protected]" target=3D"_blank">nichols01@gmail.= com</a>> <br><b>Sent:</b> Wednesday, 13 July 2022 15:20<br><b>To:</b> Sa= ulius Krasuckas <<a href=3D"mailto:[email protected]" target=3D"_blank">= [email protected]</a>><br><b>Cc:</b> Stanislav <<a href=3D"mailto:stl= [email protected]" target=3D"_blank">[email protected]</a>>; bochs-develo= pers <<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>><br><b>Subject:</= b> Re: [Bochs-developers] Before declaring Bochs is dead ...<u></u><u></u><= /span></p></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><p clas= s=3D"MsoNormal">Hello, I'm very excited to see Bochs moving to Github!<= u></u><u></u></p><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div>= <div><p class=3D"MsoNormal">I'd like to add a README.md to make the rep= o page a bit less bare.=C2=A0 Maybe this would be a good first PR to test o= ut the workflow?<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>= =C2=A0<u></u></p></div><div><p class=3D"MsoNormal">For now, I'll mostly= link into SF for e.g. documentation.=C2=A0 For bugs/managing development -= is the intention to use Github issues going forward?=C2=A0 I would be in f= avor of this (said as someone who has not contributed code... yet)<u></u><u= ></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><d= iv><p class=3D"MsoNormal"><span style=3D"color:rgb(80,0,80)">> Can someo= ne help with setting up mandatory code review for pull<br>> requests ?</= span><u></u><u></u></p></div><div><div><p class=3D"MsoNormal">I can help wi= th this if you'd like<u></u><u></u></p></div><div><p class=3D"MsoNormal= "><u></u>=C2=A0<u></u></p></div></div><div><p class=3D"MsoNormal"><u></u>= =C2=A0<u></u></p></div><div><p class=3D"MsoNormal">Thank you<u></u><u></u><= /p></div><div><p class=3D"MsoNormal">Colin<u></u><u></u></p></div><div><p c= lass=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></div><p class=3D"MsoNorma= l"><u></u>=C2=A0<u></u></p><div><div><p class=3D"MsoNormal">On Mon, Jul 11,= 2022 at 1:57 PM Saulius Krasuckas <<a href=3D"mailto:[email protected]"= target=3D"_blank">[email protected]</a>> wrote:<u></u><u></u></p></div>= <blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b= order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4= .8pt;margin-right:0cm"><p class=3D"MsoNormal">On 2022-07-11 09:26, <a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a> wro= te:<br><br>> Please take a look onto github repository:<br>> <a href= =3D"https://github.com/stlintel/Bochs" target=3D"_blank">https://github.com= /stlintel/Bochs</a><br>> and also SF git repository:<br>> <a href=3D"= https://sourceforge.net/p/bochs/bochs/ci/master/tree/" target=3D"_blank">ht= tps://sourceforge.net/p/bochs/bochs/ci/master/tree/</a><br><br>Thanks!<br><= br>> I personally prefer github interface.<br><br>Me too. I already star= red, forked the repo here, and turned on watching <br>(following) it.<br><b= r>> Can someone help with setting up mandatory code review for pull <br>= > requests ?<br><br>Not this time.=C2=A0 But maybe this paragraph or eve= n whole article could <br>give some insight:<br><a href=3D"https://github.b= log/2018-03-23-require-multiple-reviewers/#how-it-works" target=3D"_blank">= https://github.blog/2018-03-23-require-multiple-reviewers/#how-it-works</a>= <br><br>S.<br><br><br>_______________________________________________<br>bo= chs-developers mailing list<br><a href=3D"mailto:[email protected]= rceforge.net" target=3D"_blank">[email protected]</a><= br><a href=3D"https://lists.sourceforge.net/lists/listinfo/bochs-developers= " target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bochs-deve= lopers</a><u></u><u></u></p></blockquote></div></div></div></blockquote></d= iv> --0000000000000913e305e3b3a0d9-- --===============6722076483361673715== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============6722076483361673715== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ bochs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bochs-developers --===============6722076483361673715==--