* modules/inet_pton (License): Relicense under LGPLv2+.

[gnulib.git] / doc / gnulib-tool.texi

diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index f9ee261..3d6af14 100644 (file)
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -400,8 +400,11 @@ The solution is therefore:
 @enumerate
 @item
 When you run @code{gettextize}, always use the @code{gettextize} from the
-newest GNU gettext release found on @url{http://ftp.gnu.org/gnu/gettext/},
-and invoke @code{gnulib-tool} afterwards.
+matching GNU gettext release.  For the most recent Gnulib checkout, this is
+the newest release found on @url{http://ftp.gnu.org/gnu/gettext/}.  For an
+older Gnulib snapshot, it is the release that was the most recent release
+at the time the Gnulib snapshot was taken.  Then, after @code{gettextize},
+invoke @code{gnulib-tool}.
 
 @item
 When a script of yours run @code{autopoint}, invoke @code{gnulib-tool}
@@ -508,6 +511,8 @@ should be treated like generated source files, like for example a
 @item
 In projects which commit all source files, whether generated or not, into
 their VCS, the @code{gnulib-tool} generated files should all be committed.
+In this case, you also pass the option @samp{--no-vc-files} to
+@code{gnulib-tool}.
 
 Gnulib also contains files generated by @command{make} (and removed by
 @code{make clean}), using information determined by @command{configure}.