On Oct 4, 2007, at 8:18 AM, Benoit SIGOURE wrote:
I'll propose an updated version of the patch by tonight.
Patch sent. Here is a diff between the previous version and the new one. I hope my mailer won't strip spaces.
diff --git a/ChangeLog b/ChangeLog index e65615b..a0d6e30 100644 --- a/ChangeLog +++ b/ChangeLog @@ -2,8 +2,8 @@ Advertise for the Git server instead of the CVS server. * doc/gnulib-intro.texi (Steady Development): Mention the Git - * repository instead of the CVS one. - * doc/gnulib-tool.texi (CVS Issues): Rename as `SCM Issues' and + repository instead of the CVS one. + * doc/gnulib-tool.texi (CVS Issues): Rename as `VCS Issues' and adjust accordingly. * doc/gnulib.texi (Introduction): Capitalize `Git'. * doc/maintain.texi: Mention Git were relevant. Update the email diff --git a/doc/gnulib-intro.texi b/doc/gnulib-intro.texi index aa9de67..5661b44 100644 --- a/doc/gnulib-intro.texi +++ b/doc/gnulib-intro.texi@@ -277,7 +277,7 @@ Gnulib modules are continually adapted, to match new practices, to be
consistent with newly added modules, or simply as a response to buildfailure reports. We don't make releases, but instead recommend to use the newest version of Gnulib from the Git repository, except in periods of major
-changes.+changes. The source tree can also be fetched via a read-only CVS repository.
@node Openness @section Openness diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi index 8247f62..af46611 100644 --- a/doc/gnulib-tool.texi +++ b/doc/gnulib-tool.texi @@ -31,7 +31,7 @@ a real run without changing anything. * Initial import:: First import of Gnulib modules. * Modified imports:: Changing the import specification. * Simple update:: Tracking Gnulib development. -* SCM Issues:: Integration with SCMs.+* VCS Issues:: Integration with Version Control Systems.
@end menu @@ -336,8 +336,8 @@ $ gnulib-tool --import This will create, update or remove files, as needed. [EMAIL PROTECTED] SCM Issues [EMAIL PROTECTED] SCM Issues [EMAIL PROTECTED] VCS Issues [EMAIL PROTECTED] VCS Issues All files created by @code{gnulib-tool}, except @file{gnulib-cache.m4}, should be treated like generated source files, like for example a@@ -347,20 +347,20 @@ should be treated like generated source files, like for example a
@itemIn projects which commit all source files, whether generated or not, into -their SCM, the @code{gnulib-tool} generated files should all be committed. +their VCS, the @code{gnulib-tool} generated files should all be committed.
Gnulib also contains files generated by @command{make} (and removed by @code{make clean}), using information determined by @command{configure} -They should not be checked into their SCM, but instead added to +They should not be checked into their VCS, but instead added to @file{.cvsignore}. When you have a Gnulib source file of the form @file{lib/foo_.h}, the corresponding @file{lib/foo.h} is such a file. @item-In projects which customarily omit from their SCM all files that generated +In projects which customarily omit from their VCS all files that generated
from other source files, all these files and directories would not be -added into their SCM. The only file that must be added to it is +added into their VCS. The only file that must be added to it is @file{gnulib-cache.m4} in the M4 macros directory. Also, the script for -restoring files not in the SCM, customarily called @file{autogen.sh} or +restoring files not in the VCS, customarily called @file{autogen.sh} or @file{bootstrap.sh}, will typically contain the statement for restoring the omitted files: -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory
PGP.sig
Description: This is a digitally signed message part