===================================================================
@@ -0,0 +1,16 @@
+@c Copyright (C) 1988-2016 Free Software Foundation, Inc.
For a new file, just 2016 should be fine.
+In order to import a new module from gnulib, the following steps need to be executed, in order.
This line is a bit long; try to avoid more than 78 columns (80 being the
strict maximum). Same also below.
+Enter the name of the module to be imported in src/gnulib/update-gnulib.sh under IMPORTED_GNULIB_MODULES.
That is a filename, thus @file{src/gnulib/update-gnulib.sh}.
And @code{IMPORTED_GNULIB_MODULES}.
+@item
Hi Ayush, On Mon, 18 Jul 2016, ayush goel wrote: > I’m attaching a patch just containing the changes made in the /doc. a couple of comments. +Run the file update-gnulib.sh. Usage: update-gnulib.sh <path-to-gnulib-repository> I'm not completely sure whether @file{update-gnulib.sh} or @command{update-gnulib.sh}; feels like a corner case. And @var{path-to-gnulib-repository}. Invocations usally are marked up as @smallexample gcc -o out -O2 in.c plus.c @end smallexample With those changes, the documentation changes seem fine. Gerald