Re: Before declaring Bochs is dead ...
<[email protected]> Wed, 13 Jul 2022 19:41:28 +0300
| Newsgroups | gmane.comp.emulators.bochs.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multipart message in MIME format. --===============8473351655549636614== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01D896F0.8BEC5B70" Content-Language: en-il This is a multipart message in MIME format. ------=_NextPart_000_0014_01D896F0.8BEC5B70 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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. =20 From: Colin Nichols <[email protected]>=20 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 ... =20 Hello, I'm very excited to see Bochs moving to Github! =20 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? =20 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) =20 > Can someone help with setting up mandatory code review for pull > requests ? I can help with this if you'd like =20 =20 Thank you Colin =20 =20 On Mon, Jul 11, 2022 at 1:57 PM Saulius Krasuckas <[email protected] = <mailto:[email protected]> > wrote: On 2022-07-11 09:26, [email protected] <mailto:[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=20 (following) it. > Can someone help with setting up mandatory code review for pull=20 > requests ? Not this time. But maybe this paragraph or even whole article could=20 give some insight: https://github.blog/2018-03-23-require-multiple-reviewers/#how-it-works S. _______________________________________________ bochs-developers mailing list [email protected] = <mailto:[email protected]>=20 https://lists.sourceforge.net/lists/listinfo/bochs-developers ------=_NextPart_000_0014_01D896F0.8BEC5B70 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 15 (filtered = medium)"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3Den-IL link=3Dblue = vlink=3Dpurple style=3D'word-wrap:break-word'><div = class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US = style=3D'mso-fareast-language:EN-US'>Please submit a pull request. Want = to see how it looks like.<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'mso-fareast-language:EN-US'>Content doesn=E2=80=99t matter = =E2=80=93 adding README is good.<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3Den-IL = style=3D'mso-fareast-language:EN-US'><o:p> </o:p></span></p><div = style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm'><p class=3DMsoNormal><b><span = lang=3DEN-US>From:</span></b><span lang=3DEN-US> Colin Nichols = <[email protected]> <br><b>Sent:</b> Wednesday, 13 July 2022 = 15:20<br><b>To:</b> Saulius Krasuckas = <[email protected]><br><b>Cc:</b> Stanislav = <[email protected]>; bochs-developers = <[email protected]><br><b>Subject:</b> Re: = [Bochs-developers] Before declaring Bochs is dead = ...<o:p></o:p></span></p></div><p = class=3DMsoNormal><o:p> </o:p></p><div><p class=3DMsoNormal>Hello, = I'm very excited to see Bochs moving to Github!<o:p></o:p></p><div><p = class=3DMsoNormal><o:p> </o:p></p></div><div><p = class=3DMsoNormal>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?<o:p></o:p></p></div><div><p = class=3DMsoNormal><o:p> </o:p></p></div><div><p = class=3DMsoNormal>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)<o:p></o:p></p></div><div><p = class=3DMsoNormal><o:p> </o:p></p></div><div><p = class=3DMsoNormal><span style=3D'color:#500050'>> Can someone help = with setting up mandatory code review for pull<br>> requests = ?</span><o:p></o:p></p></div><div><div><p class=3DMsoNormal>I can help = with this if you'd like<o:p></o:p></p></div><div><p = class=3DMsoNormal><o:p> </o:p></p></div></div><div><p = class=3DMsoNormal><o:p> </o:p></p></div><div><p = class=3DMsoNormal>Thank you<o:p></o:p></p></div><div><p = class=3DMsoNormal>Colin<o:p></o:p></p></div><div><p = class=3DMsoNormal><o:p> </o:p></p></div></div><p = class=3DMsoNormal><o:p> </o:p></p><div><div><p class=3DMsoNormal>On = Mon, Jul 11, 2022 at 1:57 PM Saulius Krasuckas <<a = href=3D"mailto:[email protected]">[email protected]</a>> = wrote:<o:p></o:p></p></div><blockquote = style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm = 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal>On = 2022-07-11 09:26, <a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a> wrote:<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">https://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 starred, forked the repo here, and = turned on watching <br>(following) it.<br><br>> Can someone help with = setting up mandatory code review for pull <br>> requests ?<br><br>Not = this time. But maybe this paragraph or even whole article could = <br>give some insight:<br><a = href=3D"https://github.blog/2018-03-23-require-multiple-reviewers/#how-it= -works" = target=3D"_blank">https://github.blog/2018-03-23-require-multiple-reviewe= rs/#how-it-works</a><br><br>S.<br><br><br>_______________________________= ________________<br>bochs-developers mailing list<br><a = href=3D"mailto:[email protected]" = 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><o:p></o:p></p></blockquote></div></div></body></html> ------=_NextPart_000_0014_01D896F0.8BEC5B70-- --===============8473351655549636614== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============8473351655549636614== 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 --===============8473351655549636614==--