On Mon, Mar 13, 2023 at 8:07 AM Gedare Bloom <[email protected]> wrote: > > I closed it, and instead created a Pull Request from your > new-eng-chapter branch to the `master` branch on your fork of > rtems-docs > I have added comments to https://github.com/andrewbutterfield/rtems-docs/pull/1
> On Mon, Mar 13, 2023 at 3:17 AM [email protected] > <[email protected]> wrote: > > > > Hi Gedare, > > pull request done > > > > Regards, > > Andrew > > > > > > > > On 10/03/2023, 21:23, "Gedare Bloom" <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > On Fri, Mar 10, 2023 at 8:19 AM [email protected] > > <mailto:[email protected]> > > <[email protected] <mailto:[email protected]>> > > wrote: > > > > > > Hi Gedare, > > > the quick and easy way is to visit > > > https://github.com/andrewbutterfield/rtems-docs/commit/8165814471402d56c480b1400b121715ad507c58 > > > > > > <https://github.com/andrewbutterfield/rtems-docs/commit/8165814471402d56c480b1400b121715ad507c58> > > > > > Yes, In this case, can you (or I can) create a Pull Request from your > > new-eng-chapter branch to the `master` branch on your fork of > > rtems-docs? then I can review your code changes for you there pretty > > easily. > > > > > > > That's a fork of RTEMS/rtems-docs on Github - and is the top of my > > > `new-eng-chapter` branch. > > > > > > The commits are those I had developing it and do not match the patch-set > > > I sent. > > > > > > Will that do? > > > > > > Regards, > > > Andrew > > > > > > > > > > > > On 09/03/2023, 20:22, "Gedare Bloom" <[email protected] > > > <mailto:[email protected]> <mailto:[email protected] > > > <mailto:[email protected]>>> wrote: > > > > > > > > > Hi Andrew, > > > > > > > > > In this case, since the patches are attachments, would you happen to > > > have a hosted git (github?) repo that I could examine to facilitate a > > > review. I can only review inline patches efficiently by email. > > > > > > > > > Gedare > > > > > > > > > On Thu, Mar 9, 2023 at 6:52 AM [email protected] > > > <mailto:[email protected]> > > > <mailto:[email protected] > > > <mailto:[email protected]>> > > > <[email protected] <mailto:[email protected]> > > > <mailto:[email protected] > > > <mailto:[email protected]>>> wrote: > > > > > > > > ping > > > > > > > > > > > > > > > > > > > > > > > > From: devel <[email protected] <mailto:[email protected]> > > > > <mailto:[email protected] <mailto:[email protected]>>> on > > > > behalf of "[email protected] > > > > <mailto:[email protected]> > > > > <mailto:[email protected] > > > > <mailto:[email protected]>>" > > > > <[email protected] <mailto:[email protected]> > > > > <mailto:[email protected] > > > > <mailto:[email protected]>>> > > > > Date: Friday 10 February 2023 at 16:10 > > > > To: "[email protected] <mailto:[email protected]> > > > > <mailto:[email protected] <mailto:[email protected]>>" > > > > <[email protected] <mailto:[email protected]> > > > > <mailto:[email protected] <mailto:[email protected]>>> > > > > Subject: eng: Add Formal Verification chapter v3 > > > > > > > > > > > > > > > > Dear RTEMS Developers, > > > > > > > > Here is a 3rd version of the proposed Formal Verification chapter > > > > > > > > to be added to the Software Engineering Manual. > > > > > > > > > > > > > > > > The patch-set is attached here, as I cannot use git-mail. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Andrew > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > devel mailing list > > > > [email protected] <mailto:[email protected]> <mailto:[email protected] > > > > <mailto:[email protected]>> > > > > http://lists.rtems.org/mailman/listinfo/devel > > > > <http://lists.rtems.org/mailman/listinfo/devel> > > > > <http://lists.rtems.org/mailman/listinfo/devel> > > > > <http://lists.rtems.org/mailman/listinfo/devel>> > > > > > > > > > > > > > > > _______________________________________________ devel mailing list [email protected] http://lists.rtems.org/mailman/listinfo/devel
