Commit recent changes up to central repository. +
Commit changes from the working copy up to the repository.
+The cli_commitRepoChanges function uses the value of
-OPTIONVAL variable as reference to perform subversion changes
-verifications inside working copy. If cli_commitRepoChanges
-finds changes inside your working copy, it asks you for confirmation
-to commit them up to central repository.
+OPTIONVAL variable as reference to perform change verifications
+inside the working copy.
+
The cli_commitRepoChanges function brings changes from the
+repository to the working copy--using svn update--, check
+the working copy changes--using svn status command--,
+print status report--using both svn update and svn
+status commands output, and finally, commit recent changes from the
+working copy up to the repository--using svn commit
+command--.
+
Previous to commit the working copy changes up to the repository, the
+cli_commitRepoChanges function asks you to verify changes, and
+later, another confirmation question is shown to be sure you really
+want to commit changes up to central repository.
+
+ +Tip
Make small changes, document them very well, and commit +them to the repository. +
If cli_commitRepoChanges finds changes inside the working copy,
+it asks you for confirmation in order to commit them up to central
+repository.
Call cli_commitRepoChanges function after functions that modify
files inside your repository working copy.
diff --git a/Manuals/en/Info/Repository/repository.info.bz2 b/Manuals/en/Info/Repository/repository.info.bz2
index cc21138..bb36b70 100644
Binary files a/Manuals/en/Info/Repository/repository.info.bz2 and b/Manuals/en/Info/Repository/repository.info.bz2 differ
diff --git a/Manuals/en/Plaintext/Repository/repository.txt b/Manuals/en/Plaintext/Repository/repository.txt
index 3ad921e..c000594 100644
--- a/Manuals/en/Plaintext/Repository/repository.txt
+++ b/Manuals/en/Plaintext/Repository/repository.txt
@@ -2895,13 +2895,30 @@ The following global functions of `centos-art.sh' script, are available
for you to use inside specific functions:
-- Function: cli_commitRepoChanges
- Commit recent changes up to central repository.
+ Commit changes from the working copy up to the repository.
The `cli_commitRepoChanges' function uses the value of OPTIONVAL
- variable as reference to perform subversion changes verifications
- inside working copy. If `cli_commitRepoChanges' finds changes
- inside your working copy, it asks you for confirmation to commit
- them up to central repository.
+ variable as reference to perform change verifications inside the
+ working copy.
+
+ The `cli_commitRepoChanges' function brings changes from the
+ repository to the working copy--using `svn update'--, check the
+ working copy changes--using `svn status' command--, print status
+ report--using both `svn update' and `svn status' commands output,
+ and finally, commit recent changes from the working copy up to the
+ repository--using `svn commit' command--.
+
+ Previous to commit the working copy changes up to the repository,
+ the `cli_commitRepoChanges' function asks you to verify changes,
+ and later, another confirmation question is shown to be sure you
+ really want to commit changes up to central repository.
+
+ *Tip* Make small changes, document them very well, and commit
+ them to the repository.
+
+ If `cli_commitRepoChanges' finds changes inside the working copy,
+ it asks you for confirmation in order to commit them up to central
+ repository.
Call `cli_commitRepoChanges' function after functions that modify
files inside your repository working copy.
@@ -5232,24 +5249,24 @@ Index
*****
branches: See 1. (line 370)
-Common translation files: See 3.48.2.5. (line 4656)
-How to render brands' translation files: See 3.50.3. (line 4961)
-How to render fonts' translation files: See 3.52.3. (line 5038)
-How to render translation files: See 3.48.3. (line 4826)
-Metadata maintainance: See 3.43.2. (line 3800)
-Specific translation files: See 3.48.2.6. (line 4681)
+Common translation files: See 3.48.2.5. (line 4673)
+How to render brands' translation files: See 3.50.3. (line 4978)
+How to render fonts' translation files: See 3.52.3. (line 5055)
+How to render translation files: See 3.48.3. (line 4843)
+Metadata maintainance: See 3.43.2. (line 3817)
+Specific translation files: See 3.48.2.6. (line 4698)
tags: See 2. (line 373)
-Template translation files: See 3.48.2.4. (line 4486)
-Translation brands file names: See 3.50.2.1. (line 4918)
-Translation configuration scripts: See 3.48.2.8. (line 4715)
-Translation entries: See 3.48.2.1. (line 4302)
-Translation files: See 3.48.2.3. (line 4418)
-Translation markers: See 3.48.2.2. (line 4383)
-Translation paths: See 3.48.2.1. (line 4302)
+Template translation files: See 3.48.2.4. (line 4503)
+Translation brands file names: See 3.50.2.1. (line 4935)
+Translation configuration scripts: See 3.48.2.8. (line 4732)
+Translation entries: See 3.48.2.1. (line 4319)
+Translation files: See 3.48.2.3. (line 4435)
+Translation markers: See 3.48.2.2. (line 4400)
+Translation paths: See 3.48.2.1. (line 4319)
Translation pre-rendering configuration scripts:See 3.48.2.8.
- (line 4715)
-Translation rendering: See 3.48.2.7. (line 4704)
-Translation rendering default functionality: See 3.48.2.9. (line 4801)
+ (line 4732)
+Translation rendering: See 3.48.2.7. (line 4721)
+Translation rendering default functionality: See 3.48.2.9. (line 4818)
trunk: See 3. (line 376)
trunk Identity: See 3.1. (line 379)
trunk Identity Brands: See 3.2. (line 799)
@@ -5292,31 +5309,31 @@ trunk Manuals: See 3.32. (line 2355)
trunk Scripts: See 3.33. (line 2409)
trunk Scripts Bash: See 3.34. (line 2433)
trunk Scripts Bash Functions: See 3.35. (line 2545)
-trunk Scripts Bash Functions Help: See 3.36. (line 3260)
-trunk Scripts Bash Functions Html: See 3.37. (line 3281)
-trunk Scripts Bash Functions Locale: See 3.38. (line 3302)
-trunk Scripts Bash Functions Path: See 3.39. (line 3382)
-trunk Scripts Bash Functions Render: See 3.40. (line 3414)
-trunk Scripts Bash Functions Render Config: See 3.41. (line 3435)
-trunk Scripts Bash Functions Shell: See 3.42. (line 3613)
-trunk Scripts Bash Functions Svg: See 3.43. (line 3782)
-trunk Scripts Bash Functions Verify: See 3.44. (line 3970)
-trunk Scripts Bash Locale: See 3.45. (line 4186)
-trunk Scripts Perl: See 3.46. (line 4215)
-trunk Scripts Python: See 3.47. (line 4232)
-trunk Translations: See 3.48. (line 4253)
-trunk Translations Identity: See 3.49. (line 4856)
-trunk Translations Identity Brands: See 3.50. (line 4877)
-trunk Translations Identity Brands Tpl: See 3.51. (line 4972)
-trunk Translations Identity Fonts: See 3.52. (line 4987)
-trunk Translations Identity Models: See 3.53. (line 5054)
-trunk Translations Identity Release: See 3.54. (line 5069)
-trunk Translations Identity Themes: See 3.55. (line 5084)
-trunk Translations Identity Themes Backgrounds:See 3.56. (line 5099)
+trunk Scripts Bash Functions Help: See 3.36. (line 3277)
+trunk Scripts Bash Functions Html: See 3.37. (line 3298)
+trunk Scripts Bash Functions Locale: See 3.38. (line 3319)
+trunk Scripts Bash Functions Path: See 3.39. (line 3399)
+trunk Scripts Bash Functions Render: See 3.40. (line 3431)
+trunk Scripts Bash Functions Render Config: See 3.41. (line 3452)
+trunk Scripts Bash Functions Shell: See 3.42. (line 3630)
+trunk Scripts Bash Functions Svg: See 3.43. (line 3799)
+trunk Scripts Bash Functions Verify: See 3.44. (line 3987)
+trunk Scripts Bash Locale: See 3.45. (line 4203)
+trunk Scripts Perl: See 3.46. (line 4232)
+trunk Scripts Python: See 3.47. (line 4249)
+trunk Translations: See 3.48. (line 4270)
+trunk Translations Identity: See 3.49. (line 4873)
+trunk Translations Identity Brands: See 3.50. (line 4894)
+trunk Translations Identity Brands Tpl: See 3.51. (line 4989)
+trunk Translations Identity Fonts: See 3.52. (line 5004)
+trunk Translations Identity Models: See 3.53. (line 5071)
+trunk Translations Identity Release: See 3.54. (line 5086)
+trunk Translations Identity Themes: See 3.55. (line 5101)
+trunk Translations Identity Themes Backgrounds:See 3.56. (line 5116)
trunk Translations Identity Themes Distro Anaconda Progress:See 3.57.
- (line 5120)
-trunk Translations Identity Widgets: See 3.58. (line 5213)
-Unused definitions: See 3.43.2.1. (line 3907)
+ (line 5137)
+trunk Translations Identity Widgets: See 3.58. (line 5230)
+Unused definitions: See 3.43.2.1. (line 3924)
List of Figures
***************
diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi
index 4213743..440c5b4 100644
--- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi
+++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi
@@ -375,13 +375,34 @@ The following global functions of @file{centos-art.sh} script, are
available for you to use inside specific functions:
@defun cli_commitRepoChanges
-Commit recent changes up to central repository.
+Commit changes from the working copy up to the repository.
+
The @code{cli_commitRepoChanges} function uses the value of
-@var{OPTIONVAL} variable as reference to perform subversion changes
-verifications inside working copy. If @code{cli_commitRepoChanges}
-finds changes inside your working copy, it asks you for confirmation
-to commit them up to central repository.
+@var{OPTIONVAL} variable as reference to perform change verifications
+inside the working copy.
+
+The @code{cli_commitRepoChanges} function brings changes from the
+repository to the working copy---using @command{svn update}---, check
+the working copy changes---using @command{svn status} command---,
+print status report---using both @command{svn update} and @command{svn
+status} commands output, and finally, commit recent changes from the
+working copy up to the repository---using @command{svn commit}
+command---.
+
+Previous to commit the working copy changes up to the repository, the
+@code{cli_commitRepoChanges} function asks you to verify changes, and
+later, another confirmation question is shown to be sure you really
+want to commit changes up to central repository.
+
+@quotation
+@strong{Tip} Make small changes, document them very well, and commit
+them to the repository.
+@end quotation
+
+If @code{cli_commitRepoChanges} finds changes inside the working copy,
+it asks you for confirmation in order to commit them up to central
+repository.
Call @code{cli_commitRepoChanges} function after functions that modify
files inside your repository working copy.