Fossil SCM

[/help/update|update] doc improvements from the ML.

stephan 2014-07-31 20:54 trunk
Commit 8ab520c5896c8ff3b75c63407a78c1e502c4e767
Parent 2ba71f510583dcc…
1 file changed +24 -18
~ src/update.c
M src/update.c
+24 -18
--- src/update.c
+++ src/update.c
@@ -62,31 +62,37 @@
6262
 /*
6363
 ** COMMAND: update
6464
 **
6565
 ** Usage: %fossil update ?OPTIONS? ?VERSION? ?FILES...?
6666
 **
67
-** Change the version of the current checkout to VERSION. Any uncommitted
68
-** changes are retained and applied to the new checkout.
67
+** Change the version of the current checkout to VERSION. Any
68
+** uncommitted changes are retained and applied to the new checkout.
6969
 **
70
-** The VERSION argument can be a specific version or tag or branch name.
71
-** If the VERSION argument is omitted, then the leaf of the subtree
72
-** that begins at the current version is used, if there is only a single
73
-** leaf. VERSION can also be "current" to select the leaf of the current
74
-** version or "latest" to select the most recent check-in.
70
+** The VERSION argument can be a specific version or tag or branch
71
+** name. If the VERSION argument is omitted, then the leaf of the
72
+** subtree that begins at the current version is used, if there is
73
+** only a single leaf. VERSION can also be "current" to select the
74
+** leaf of the current version or "latest" to select the most recent
75
+** check-in.
7576
 **
7677
 ** If one or more FILES are listed after the VERSION then only the
77
-** named files are candidates to be updated. If FILES is omitted, all
78
-** files in the current checkout are subject to be updated. Using
79
-** a directory name for one of the FILES arguments is the same as
80
-** using every subdirectory and file beneath that directory.
81
-**
82
-** The -n or --dry-run option causes this command to do a "dry run". It
83
-** prints out what would have happened but does not actually make any
84
-** changes to the current checkout or the repository.
85
-**
86
-** The -v or --verbose option prints status information about unchanged
87
-** files in addition to those file that actually do change.
78
+** named files are candidates to be updated, and any updates to them
79
+** will be treated as edits to the current version. Using a directory
80
+** name for one of the FILES arguments is the same as using every
81
+** subdirectory and file beneath that directory.
82
+**
83
+** If FILES is omitted, all files in the current checkout are subject
84
+** to being updated and the version of the current checkout is changed
85
+** to VERSION. Any uncommitted changes are retained and applied to the
86
+** new checkout.
87
+**
88
+** The -n or --dry-run option causes this command to do a "dry run".
89
+** It prints out what would have happened but does not actually make
90
+** any changes to the current checkout or the repository.
91
+**
92
+** The -v or --verbose option prints status information about
93
+** unchanged files in addition to those file that actually do change.
8894
 **
8995
 ** Options:
9096
 ** --case-sensitive <BOOL> override case-sensitive setting
9197
 ** --debug print debug information on stdout
9298
 ** --latest acceptable in place of VERSION, update to latest version
9399
--- src/update.c
+++ src/update.c
@@ -62,31 +62,37 @@
62 /*
63 ** COMMAND: update
64 **
65 ** Usage: %fossil update ?OPTIONS? ?VERSION? ?FILES...?
66 **
67 ** Change the version of the current checkout to VERSION. Any uncommitted
68 ** changes are retained and applied to the new checkout.
69 **
70 ** The VERSION argument can be a specific version or tag or branch name.
71 ** If the VERSION argument is omitted, then the leaf of the subtree
72 ** that begins at the current version is used, if there is only a single
73 ** leaf. VERSION can also be "current" to select the leaf of the current
74 ** version or "latest" to select the most recent check-in.
 
75 **
76 ** If one or more FILES are listed after the VERSION then only the
77 ** named files are candidates to be updated. If FILES is omitted, all
78 ** files in the current checkout are subject to be updated. Using
79 ** a directory name for one of the FILES arguments is the same as
80 ** using every subdirectory and file beneath that directory.
81 **
82 ** The -n or --dry-run option causes this command to do a "dry run". It
83 ** prints out what would have happened but does not actually make any
84 ** changes to the current checkout or the repository.
85 **
86 ** The -v or --verbose option prints status information about unchanged
87 ** files in addition to those file that actually do change.
 
 
 
 
 
88 **
89 ** Options:
90 ** --case-sensitive <BOOL> override case-sensitive setting
91 ** --debug print debug information on stdout
92 ** --latest acceptable in place of VERSION, update to latest version
93
--- src/update.c
+++ src/update.c
@@ -62,31 +62,37 @@
62 /*
63 ** COMMAND: update
64 **
65 ** Usage: %fossil update ?OPTIONS? ?VERSION? ?FILES...?
66 **
67 ** Change the version of the current checkout to VERSION. Any
68 ** uncommitted changes are retained and applied to the new checkout.
69 **
70 ** The VERSION argument can be a specific version or tag or branch
71 ** name. If the VERSION argument is omitted, then the leaf of the
72 ** subtree that begins at the current version is used, if there is
73 ** only a single leaf. VERSION can also be "current" to select the
74 ** leaf of the current version or "latest" to select the most recent
75 ** check-in.
76 **
77 ** If one or more FILES are listed after the VERSION then only the
78 ** named files are candidates to be updated, and any updates to them
79 ** will be treated as edits to the current version. Using a directory
80 ** name for one of the FILES arguments is the same as using every
81 ** subdirectory and file beneath that directory.
82 **
83 ** If FILES is omitted, all files in the current checkout are subject
84 ** to being updated and the version of the current checkout is changed
85 ** to VERSION. Any uncommitted changes are retained and applied to the
86 ** new checkout.
87 **
88 ** The -n or --dry-run option causes this command to do a "dry run".
89 ** It prints out what would have happened but does not actually make
90 ** any changes to the current checkout or the repository.
91 **
92 ** The -v or --verbose option prints status information about
93 ** unchanged files in addition to those file that actually do change.
94 **
95 ** Options:
96 ** --case-sensitive <BOOL> override case-sensitive setting
97 ** --debug print debug information on stdout
98 ** --latest acceptable in place of VERSION, update to latest version
99

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button