From 38d0aba0f3a4bea3534ac91cc740f55e3542fb0d Mon Sep 17 00:00:00 2001 From: Eric Blake Date: Mon, 8 Mar 2010 14:26:11 -0700 Subject: [PATCH] gnulib-tool.texi: mention possibility of git submodule * doc/gnulib-tool.texi (VCS Issues): Add paragraph about using git submodules. Signed-off-by: Eric Blake --- ChangeLog | 6 ++++++ doc/gnulib-tool.texi | 9 ++++++++- 2 files changed, 14 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog index 25a771a..a81fb36 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2010-03-08 Eric Blake + + gnulib-tool.texi: mention possibility of git submodule + * doc/gnulib-tool.texi (VCS Issues): Add paragraph about using git + submodules. + 2010-03-08 Karl Berry * doc/gnulib-tool.texi (VCS Issues): Mention third option diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi index 1c39659..5d3d5db 100644 --- a/doc/gnulib-tool.texi +++ b/doc/gnulib-tool.texi @@ -578,7 +578,7 @@ VCS Issues are added into the VCS. The only file that must be added to the VCS is @file{gnulib-cache.m4} in the M4 macros directory. Also, the script for restoring files not in the VCS, customarily called address@hidden or @file{bootstrap.sh}, will typically contain the address@hidden or @file{bootstrap}, will typically contain the statement for restoring the omitted files: @smallexample @@ -590,6 +590,13 @@ VCS Issues Also it does not report in the ChangeLogs the files that it had to add because they were missing. +Gnulib includes the file @file{build-aux/bootstrap} to aid a developer +in using this setup. Furthermore, in projects that use git for +version control, it is possible to use a git submodule containing the +precise commit of the gnulib repository, so that each developer +running @file{bootstrap} will get the same version of all +gnulib-provided files. + @item Some projects take a ``middle road'': they do commit Gnulib source files as in the first approach, but they do not commit other derived -- 1.6.6.1