There was a problem with building latex pdf docs, it turned out to be some invisible unicode that slipped in the GSoC Getting Started patch.
On Thu, Apr 2, 2020 at 12:15 PM Gedare Bloom <ged...@rtems.org> wrote: > > Module: rtems-docs > Branch: master > Commit: d4d30673d094e1e7c796c5a6d3de3e12ccaa1b9e > Changeset: > http://git.rtems.org/rtems-docs/commit/?id=d4d30673d094e1e7c796c5a6d3de3e12ccaa1b9e > > Author: Gedare Bloom <ged...@rtems.org> > Date: Thu Apr 2 12:14:51 2020 -0600 > > user/start/gsoc: fix unicode error and grammar typo > > --- > > user/start/gsoc.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/user/start/gsoc.rst b/user/start/gsoc.rst > index 62154ff..7f27d7b 100644 > --- a/user/start/gsoc.rst > +++ b/user/start/gsoc.rst > @@ -21,7 +21,7 @@ subsections under :ref:`Quick Start <QuickStart>` chapter > or ask on the > :r:list:`devel`. > > You will be best served by using a GNU/Linux environment, which could be in a > -virtual machine, for example that uses `Virtualbox > <https://www.virtualbox.org/>`_ > +virtual machine, for example that uses `Virtualbox > <https://www.virtualbox.org/>`_ > and should run on most modern desktop systems. You should also be able to > work > with a MacOS or Windows system, but might encounter more difficulty than a > *nix > environment. > @@ -129,4 +129,4 @@ Here are a few pointers to keep in mind while creating > the patches. > * Avoid trailing whitespace errors. > * The author name of the patch is your full name. > * The author email of the patch is your valid email address. > -* Ensure that your patch builds before sending them for review. > \ No newline at end of file > +* Ensure that your patches build before sending them for review. > > _______________________________________________ > vc mailing list > v...@rtems.org > http://lists.rtems.org/mailman/listinfo/vc _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
