|
From: Colin N. <nic...@gm...> - 2022-07-13 18:05:17
|
Done - https://github.com/stlintel/Bochs/pull/1 On Wed, Jul 13, 2022 at 12:41 PM <stl...@gm...> wrote: > Please submit a pull request. Want to see how it looks like. > > Content doesn’t matter – adding README is good. > > > > *From:* Colin Nichols <nic...@gm...> > *Sent:* Wednesday, 13 July 2022 15:20 > *To:* Saulius Krasuckas <sau...@ar...> > *Cc:* Stanislav <stl...@gm...>; bochs-developers < > boc...@li...> > *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 <sau...@ar...> > wrote: > > On 2022-07-11 09:26, stl...@gm... 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 > boc...@li... > https://lists.sourceforge.net/lists/listinfo/bochs-developers > > |