Fossil SCM

Added clarification note for merge command.

brickviking 2024-11-07 01:09 bv-corrections01
Commit a35cfda912e476ba1cd24f5dc22fde240ff408bedfe3caca9be37cc5e168e686
1 file changed +3
--- src/merge.c
+++ src/merge.c
@@ -295,10 +295,13 @@
295295
** Files which are renamed in the merged-in branch will be renamed in
296296
** the current check-out.
297297
**
298298
** If the VERSION argument is omitted, then Fossil attempts to find
299299
** a recent fork on the current branch to merge.
300
+**
301
+** Note that this command does not commit the merge, as that is a
302
+** separate step.
300303
**
301304
** If there are multiple VERSION arguments, then each VERSION is merged
302305
** (or cherrypicked) in the order that they appear on the command-line.
303306
**
304307
** Options:
305308
--- src/merge.c
+++ src/merge.c
@@ -295,10 +295,13 @@
295 ** Files which are renamed in the merged-in branch will be renamed in
296 ** the current check-out.
297 **
298 ** If the VERSION argument is omitted, then Fossil attempts to find
299 ** a recent fork on the current branch to merge.
 
 
 
300 **
301 ** If there are multiple VERSION arguments, then each VERSION is merged
302 ** (or cherrypicked) in the order that they appear on the command-line.
303 **
304 ** Options:
305
--- src/merge.c
+++ src/merge.c
@@ -295,10 +295,13 @@
295 ** Files which are renamed in the merged-in branch will be renamed in
296 ** the current check-out.
297 **
298 ** If the VERSION argument is omitted, then Fossil attempts to find
299 ** a recent fork on the current branch to merge.
300 **
301 ** Note that this command does not commit the merge, as that is a
302 ** separate step.
303 **
304 ** If there are multiple VERSION arguments, then each VERSION is merged
305 ** (or cherrypicked) in the order that they appear on the command-line.
306 **
307 ** Options:
308

Keyboard Shortcuts

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