doc: format pathnames and URLs as monospace.
Applying CodingGuidelines about monospace on pathnames and URLs. See Documentation/CodingGuidelines.txt for more information. Signed-off-by: Corentin BOMPARD <corentin.bompard@etu.univ-lyon1.fr> Signed-off-by: Nathan BERBEZIER <nathan.berbezier@etu.univ-lyon1.fr> Signed-off-by: Pablo CHABANNE <pablo.chabanne@etu.univ-lyon1.fr> Signed-off-by: Matthieu MOY <matthieu.moy@univ-lyon1.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Corentin BOMPARD committed
Mar 6, 2019 at 14:04 UTC
68ed71b53cf7c58343306566fa6d527cb5fced41
17 files changed
+65
-65
Documentation/SubmittingPatches
+3
-3
@@ -372,15 +372,15 @@ such as "Thanks-to:", "Based-on-patch-by:", or "Mentored-by:".
372
Some parts of the system have dedicated maintainers with their own
373
repositories.
374
375
-- 'git-gui/' comes from git-gui project, maintained by Pat Thoyts:
375
+- `git-gui/` comes from git-gui project, maintained by Pat Thoyts:
376
377
git://repo.or.cz/git-gui.git
378
379
-- 'gitk-git/' comes from Paul Mackerras's gitk project:
379
+- `gitk-git/` comes from Paul Mackerras's gitk project:
380
381
git://ozlabs.org/~paulus/gitk
382
383
-- 'po/' comes from the localization coordinator, Jiang Xin:
383
+- `po/` comes from the localization coordinator, Jiang Xin:
384
385
https://github.com/git-l10n/git-po/
386
Documentation/config/core.txt
+7
-7
@@ -414,7 +414,7 @@ Common unit suffixes of 'k', 'm', or 'g' are supported.
414
core.excludesFile::
415
Specifies the pathname to the file that contains patterns to
416
describe paths that are not meant to be tracked, in addition
417
- to '.gitignore' (per-directory) and '.git/info/exclude'.
417
+ to `.gitignore` (per-directory) and `.git/info/exclude`.
418
Defaults to `$XDG_CONFIG_HOME/git/ignore`.
419
If `$XDG_CONFIG_HOME` is either not set or empty, `$HOME/.config/git/ignore`
420
is used instead. See linkgit:gitignore[5].
@@ -429,8 +429,8 @@ core.askPass::
429
command-line argument and write the password on its STDOUT.
430
431
core.attributesFile::
432
- In addition to '.gitattributes' (per-directory) and
433
- '.git/info/attributes', Git looks into this file for attributes
432
+ In addition to `.gitattributes` (per-directory) and
433
+ `.git/info/attributes`, Git looks into this file for attributes
434
(see linkgit:gitattributes[5]). Path expansions are made the same
435
way as for `core.excludesFile`. Its default value is
436
`$XDG_CONFIG_HOME/git/attributes`. If `$XDG_CONFIG_HOME` is either not
@@ -438,10 +438,10 @@ core.attributesFile::
438
439
core.hooksPath::
440
By default Git will look for your hooks in the
441
- '$GIT_DIR/hooks' directory. Set this to different path,
442
- e.g. '/etc/git/hooks', and Git will try to find your hooks in
443
- that directory, e.g. '/etc/git/hooks/pre-receive' instead of
444
- in '$GIT_DIR/hooks/pre-receive'.
441
+ `$GIT_DIR/hooks` directory. Set this to different path,
442
+ e.g. `/etc/git/hooks`, and Git will try to find your hooks in
443
+ that directory, e.g. `/etc/git/hooks/pre-receive` instead of
444
+ in `$GIT_DIR/hooks/pre-receive`.
445
+
446
The path can be either absolute or relative. A relative path is
447
taken as relative to the directory where the hooks are run (see
Documentation/git-daemon.txt
+1
-1
@@ -57,7 +57,7 @@ OPTIONS
57
This is sort of "Git root" - if you run 'git daemon' with
58
'--base-path=/srv/git' on example.com, then if you later try to pull
59
'git://example.com/hello.git', 'git daemon' will interpret the path
60
- as '/srv/git/hello.git'.
60
+ as `/srv/git/hello.git`.
61
62
--base-path-relaxed::
63
If --base-path is enabled and repo lookup fails, with this option
Documentation/git-filter-branch.txt
+1
-1
@@ -189,7 +189,7 @@ to other tags will be rewritten to point to the underlying commit.
189
rewriting. When applying a tree filter, the command needs to
190
temporarily check out the tree to some directory, which may consume
191
considerable space in case of large projects. By default it
192
- does this in the '.git-rewrite/' directory but you can override
192
+ does this in the `.git-rewrite/` directory but you can override
193
that choice by this parameter.
194
195
-f::
Documentation/git-help.txt
+2
-2
@@ -171,8 +171,8 @@ variable, we launch 'kfmclient' to try to open the man page on an
171
already opened konqueror in a new tab if possible.
172
173
For consistency, we also try such a trick if 'man.konqueror.path' is
174
-set to something like 'A_PATH_TO/konqueror'. That means we will try to
175
-launch 'A_PATH_TO/kfmclient' instead.
174
+set to something like `A_PATH_TO/konqueror`. That means we will try to
175
+launch `A_PATH_TO/kfmclient` instead.
176
177
If you really want to use 'konqueror', then you can use something like
178
the following:
Documentation/git-ls-tree.txt
+2
-2
@@ -27,9 +27,9 @@ in the current working directory. Note that:
27
taken as relative to the current working directory. E.g. when you are
28
in a directory 'sub' that has a directory 'dir', you can run 'git
29
ls-tree -r HEAD dir' to list the contents of the tree (that is
30
- 'sub/dir' in `HEAD`). You don't want to give a tree that is not at the
30
+ `sub/dir` in `HEAD`). You don't want to give a tree that is not at the
31
root level (e.g. `git ls-tree -r HEAD:sub dir`) in this case, as that
32
- would result in asking for 'sub/sub/dir' in the `HEAD` commit.
32
+ would result in asking for `sub/sub/dir` in the `HEAD` commit.
33
However, the current working directory can be ignored by passing
34
--full-tree option.
35
Documentation/git-remote-ext.txt
+1
-1
@@ -104,7 +104,7 @@ begins with `ext::`. Examples:
104
link-level address).
105
106
"ext::git-server-alias foo %G/repo% with% spaces %Vfoo"::
107
- Represents a repository with path '/repo with spaces' accessed
107
+ Represents a repository with path `/repo with spaces` accessed
108
using the helper program "git-server-alias foo". The hostname for
109
the remote server passed in the protocol stream will be "foo"
110
(this allows multiple virtual Git servers to share a
Documentation/git-submodule.txt
+1
-1
@@ -38,7 +38,7 @@ This may be either an absolute URL, or (if it begins with ./
38
or ../), the location relative to the superproject's default remote
39
repository (Please note that to specify a repository 'foo.git'
40
which is located right next to a superproject 'bar.git', you'll
41
-have to use '../foo.git' instead of './foo.git' - as one might expect
41
+have to use `../foo.git` instead of `./foo.git` - as one might expect
42
when following the rules for relative URLs - because the evaluation
43
of relative URLs in Git is identical to that of relative directories).
44
+
Documentation/git-web--browse.txt
+2
-2
@@ -92,8 +92,8 @@ configuration variable, we launch 'kfmclient' to try to open the HTML
92
man page on an already opened konqueror in a new tab if possible.
93
94
For consistency, we also try such a trick if 'browser.konqueror.path' is
95
-set to something like 'A_PATH_TO/konqueror'. That means we will try to
96
-launch 'A_PATH_TO/kfmclient' instead.
95
+set to something like `A_PATH_TO/konqueror`. That means we will try to
96
+launch `A_PATH_TO/kfmclient` instead.
97
98
If you really want to use 'konqueror', then you can use something like
99
the following:
Documentation/gitk.txt
+4
-4
@@ -168,12 +168,12 @@ Files
168
-----
169
User configuration and preferences are stored at:
170
171
-* '$XDG_CONFIG_HOME/git/gitk' if it exists, otherwise
172
-* '$HOME/.gitk' if it exists
171
+* `$XDG_CONFIG_HOME/git/gitk` if it exists, otherwise
172
+* `$HOME/.gitk` if it exists
173
174
-If neither of the above exist then '$XDG_CONFIG_HOME/git/gitk' is created and
174
+If neither of the above exist then `$XDG_CONFIG_HOME/git/gitk` is created and
175
used by default. If '$XDG_CONFIG_HOME' is not set it defaults to
176
-'$HOME/.config' in all cases.
176
+`$HOME/.config` in all cases.
177
178
History
179
-------
Documentation/gitmodules.txt
+1
-1
@@ -115,7 +115,7 @@ Consider the following .gitmodules file:
115
116
117
This defines two submodules, `libfoo` and `libbar`. These are expected to
118
-be checked out in the paths 'include/foo' and 'include/bar', and for both
118
+be checked out in the paths `include/foo` and `include/bar`, and for both
119
submodules a URL is specified which can be used for cloning the submodules.
120
121
SEE ALSO
Documentation/gitrepository-layout.txt
+1
-1
@@ -84,7 +84,7 @@ objects/info/alternates::
84
to the object database, not to the repository!) in your
85
alternates file, but it will not work if you use absolute
86
paths unless the absolute path in filesystem and web URL
87
- is the same. See also 'objects/info/http-alternates'.
87
+ is the same. See also `objects/info/http-alternates`.
88
89
objects/info/http-alternates::
90
This file records URLs to alternate object stores that
Documentation/gitweb.conf.txt
+15
-15
@@ -50,11 +50,11 @@ following order:
50
* built-in values (some set during build stage),
51
52
* common system-wide configuration file (defaults to
53
- '/etc/gitweb-common.conf'),
53
+ `/etc/gitweb-common.conf`),
54
55
* either per-instance configuration file (defaults to 'gitweb_config.perl'
56
in the same directory as the installed gitweb), or if it does not exists
57
- then fallback system-wide configuration file (defaults to '/etc/gitweb.conf').
57
+ then fallback system-wide configuration file (defaults to `/etc/gitweb.conf`).
58
59
Values obtained in later configuration files override values obtained earlier
60
in the above sequence.
@@ -82,7 +82,7 @@ You can include other configuration file using read_config_file()
82
subroutine. For example, one might want to put gitweb configuration
83
related to access control for viewing repositories via Gitolite (one
84
of Git repository management tools) in a separate file, e.g. in
85
-'/etc/gitweb-gitolite.conf'. To include it, put
85
+`/etc/gitweb-gitolite.conf`. To include it, put
86
87
--------------------------------------------------
88
read_config_file("/etc/gitweb-gitolite.conf");
@@ -142,7 +142,7 @@ and its path_info based equivalent
142
http://git.example.com/gitweb.cgi/foo/bar.git
143
------------------------------------------------
144
+
145
-will map to the path '/srv/git/foo/bar.git' on the filesystem.
145
+will map to the path `/srv/git/foo/bar.git` on the filesystem.
146
147
$projects_list::
148
Name of a plain text file listing projects, or a name of directory
@@ -234,9 +234,9 @@ $GIT::
234
235
$mimetypes_file::
236
File to use for (filename extension based) guessing of MIME types before
237
- trying '/etc/mime.types'. *NOTE* that this path, if relative, is taken
237
+ trying `/etc/mime.types`. *NOTE* that this path, if relative, is taken
238
as relative to the current Git repository, not to CGI script. If unset,
239
- only '/etc/mime.types' is used (if present on filesystem). If no mimetypes
239
+ only `/etc/mime.types` is used (if present on filesystem). If no mimetypes
240
file is found, mimetype guessing based on extension of file is disabled.
241
Unset by default.
242
@@ -297,8 +297,8 @@ relative to base URI of gitweb.
297
+
298
This list should contain the URI of gitweb's standard stylesheet. The default
299
URI of gitweb stylesheet can be set at build time using the `GITWEB_CSS`
300
-makefile variable. Its default value is 'static/gitweb.css'
301
-(or 'static/gitweb.min.css' if the `CSSMIN` variable is defined,
300
+makefile variable. Its default value is `static/gitweb.css`
301
+(or `static/gitweb.min.css` if the `CSSMIN` variable is defined,
302
i.e. if CSS minifier is used during build).
303
+
304
*Note*: there is also a legacy `$stylesheet` configuration variable, which was
@@ -311,7 +311,7 @@ $logo::
311
is displayed in the top right corner of each gitweb page and used as
312
a logo for the Atom feed. Relative to the base URI of gitweb (as a path).
313
Can be adjusted when building gitweb using `GITWEB_LOGO` variable
314
- By default set to 'static/git-logo.png'.
314
+ By default set to `static/git-logo.png`.
315
316
$favicon::
317
Points to the location where you put 'git-favicon.png' on your web
@@ -320,7 +320,7 @@ $favicon::
320
may display them in the browser's URL bar and next to the site name in
321
bookmarks. Relative to the base URI of gitweb. Can be adjusted at
322
build time using `GITWEB_FAVICON` variable.
323
- By default set to 'static/git-favicon.png'.
323
+ By default set to `static/git-favicon.png`.
324
325
$javascript::
326
Points to the location where you put 'gitweb.js' on your web server,
@@ -328,7 +328,7 @@ $javascript::
328
Relative to the base URI of gitweb. Can be set at build time using
329
the `GITWEB_JS` build-time configuration variable.
330
+
331
-The default value is either 'static/gitweb.js', or 'static/gitweb.min.js' if
331
+The default value is either `static/gitweb.js`, or `static/gitweb.min.js` if
332
the `JSMIN` build variable was defined, i.e. if JavaScript minifier was used
333
at build time. *Note* that this single file is generated from multiple
334
individual JavaScript "modules".
@@ -444,7 +444,7 @@ $default_blob_plain_mimetype::
444
doesn't result in some other type; by default "text/plain".
445
Gitweb guesses mimetype of a file to display based on extension
446
of its filename, using `$mimetypes_file` (if set and file exists)
447
- and '/etc/mime.types' files (see *mime.types*(5) manpage; only
447
+ and `/etc/mime.types` files (see *mime.types*(5) manpage; only
448
filename extension rules are supported by gitweb).
449
450
$default_text_plain_charset::
@@ -486,7 +486,7 @@ affects how "summary" pages look like, or load limiting).
486
(for example one for `git://` protocol, and one for `http://`
487
protocol).
488
+
489
-Note that per repository configuration can be set in '$GIT_DIR/cloneurl'
489
+Note that per repository configuration can be set in `$GIT_DIR/cloneurl`
490
file, or as values of multi-value `gitweb.url` configuration variable in
491
project config. Per-repository configuration takes precedence over value
492
composed from `@git_base_url_list` elements and project name.
@@ -520,7 +520,7 @@ $maxload::
520
If the server load exceeds this value then gitweb will return
521
"503 Service Unavailable" error. The server load is taken to be 0
522
if gitweb cannot determine its value. Currently it works only on Linux,
523
- where it uses '/proc/loadavg'; the load there is the number of active
523
+ where it uses `/proc/loadavg`; the load there is the number of active
524
tasks on the system -- processes that are actually running -- averaged
525
over the last minute.
526
+
@@ -739,7 +739,7 @@ Currently available providers are *"gravatar"* and *"picon"*.
739
Only one provider at a time can be selected ('default' is one element list).
740
If an unknown provider is specified, the feature is disabled.
741
*Note* that some providers might require extra Perl packages to be
742
-installed; see 'gitweb/INSTALL' for more details.
742
+installed; see `gitweb/INSTALL` for more details.
743
+
744
This feature can be configured on a per-repository basis via
745
repository's `gitweb.avatar` configuration variable.
Documentation/gitweb.txt
+19
-19
@@ -36,7 +36,7 @@ browsed using gitweb itself.
36
CONFIGURATION
37
-------------
38
Various aspects of gitweb's behavior can be controlled through the configuration
39
-file 'gitweb_config.perl' or '/etc/gitweb.conf'. See the linkgit:gitweb.conf[5]
39
+file `gitweb_config.perl` or `/etc/gitweb.conf`. See the linkgit:gitweb.conf[5]
40
for details.
41
42
Repositories
@@ -51,7 +51,7 @@ projects' root" subsection).
51
our $projectroot = '/path/to/parent/directory';
52
-----------------------------------------------------------------------
53
54
-The default value for `$projectroot` is '/pub/git'. You can change it during
54
+The default value for `$projectroot` is `/pub/git`. You can change it during
55
building gitweb via `GITWEB_PROJECTROOT` build configuration variable.
56
57
By default all Git repositories under `$projectroot` are visible and available
@@ -231,7 +231,7 @@ Unnamed repository; edit this file to name it for gitweb.
231
-------------------------------------------------------------------------------
232
+
233
from the template during repository creation, usually installed in
234
-'/usr/share/git-core/templates/'. You can use the `gitweb.description` repo
234
+`/usr/share/git-core/templates/`. You can use the `gitweb.description` repo
235
configuration variable, but the file takes precedence.
236
237
category (or `gitweb.category`)::
@@ -407,7 +407,7 @@ in the instructions so they can be included in a future release.
407
Apache as CGI
408
~~~~~~~~~~~~~
409
Apache must be configured to support CGI scripts in the directory in
410
-which gitweb is installed. Let's assume that it is '/var/www/cgi-bin'
410
+which gitweb is installed. Let's assume that it is `/var/www/cgi-bin`
411
directory.
412
413
-----------------------------------------------------------------------
@@ -431,7 +431,7 @@ You can use mod_perl with gitweb. You must install Apache::Registry
431
(for mod_perl 1.x) or ModPerl::Registry (for mod_perl 2.x) to enable
432
this support.
433
434
-Assuming that gitweb is installed to '/var/www/perl', the following
434
+Assuming that gitweb is installed to `/var/www/perl`, the following
435
Apache configuration (for mod_perl 2.x) is suitable.
436
437
-----------------------------------------------------------------------
@@ -456,7 +456,7 @@ Apache with FastCGI
456
~~~~~~~~~~~~~~~~~~~
457
Gitweb works with Apache and FastCGI. First you need to rename, copy
458
or symlink gitweb.cgi to gitweb.fcgi. Let's assume that gitweb is
459
-installed in '/usr/share/gitweb' directory. The following Apache
459
+installed in `/usr/share/gitweb` directory. The following Apache
460
configuration is suitable (UNTESTED!)
461
462
-----------------------------------------------------------------------
@@ -503,22 +503,22 @@ repositories, you can configure Apache like this:
503
-----------------------------------------------------------------------
504
505
The above configuration expects your public repositories to live under
506
-'/pub/git' and will serve them as `http://git.domain.org/dir-under-pub-git`,
506
+`/pub/git` and will serve them as `http://git.domain.org/dir-under-pub-git`,
507
both as clonable Git URL and as browseable gitweb interface. If you then
508
start your linkgit:git-daemon[1] with `--base-path=/pub/git --export-all`
509
then you can even use the `git://` URL with exactly the same path.
510
511
Setting the environment variable `GITWEB_CONFIG` will tell gitweb to use the
512
-named file (i.e. in this example '/etc/gitweb.conf') as a configuration for
512
+named file (i.e. in this example `/etc/gitweb.conf`) as a configuration for
513
gitweb. You don't really need it in above example; it is required only if
514
your configuration file is in different place than built-in (during
515
-compiling gitweb) 'gitweb_config.perl' or '/etc/gitweb.conf'. See
515
+compiling gitweb) 'gitweb_config.perl' or `/etc/gitweb.conf`. See
516
linkgit:gitweb.conf[5] for details, especially information about precedence
517
rules.
518
519
If you use the rewrite rules from the example you *might* also need
520
something like the following in your gitweb configuration file
521
-('/etc/gitweb.conf' following example):
521
+(`/etc/gitweb.conf` following example):
522
----------------------------------------------------------------------------
523
@stylesheets = ("/some/absolute/path/gitweb.css");
524
$my_uri = "/";
@@ -575,7 +575,7 @@ like this:
575
576
Here actual project root is passed to gitweb via `GITWEB_PROJECT_ROOT`
577
environment variable from a web server, so you need to put the following
578
-line in gitweb configuration file ('/etc/gitweb.conf' in above example):
578
+line in gitweb configuration file (`/etc/gitweb.conf` in above example):
579
--------------------------------------------------------------------------
580
$projectroot = $ENV{'GITWEB_PROJECTROOT'} || "/pub/git";
581
--------------------------------------------------------------------------
@@ -585,7 +585,7 @@ referenced by `$per_request_config`;
585
586
These configurations enable two things. First, each unix user (`<user>`) of
587
the server will be able to browse through gitweb Git repositories found in
588
-'~/public_git/' with the following url:
588
+`~/public_git/` with the following url:
589
590
http://git.example.org/~<user>/
591
@@ -596,7 +596,7 @@ If you already use `mod_userdir` in your virtual host or you don't want to
596
use the \'~' as first character, just comment or remove the second rewrite
597
rule, and uncomment one of the following according to what you want.
598
599
-Second, repositories found in '/pub/scm/' and '/var/git/' will be accessible
599
+Second, repositories found in `/pub/scm/` and `/var/git/` will be accessible
600
through `http://git.example.org/scm/` and `http://git.example.org/var/`.
601
You can add as many project roots as you want by adding rewrite rules like
602
the third and the fourth.
@@ -614,7 +614,7 @@ that it consumes and produces URLs in the form
614
http://git.example.com/project.git/shortlog/sometag
615
616
i.e. without 'gitweb.cgi' part, by using a configuration such as the
617
-following. This configuration assumes that '/var/www/gitweb' is the
617
+following. This configuration assumes that `/var/www/gitweb` is the
618
DocumentRoot of your webserver, contains the gitweb.cgi script and
619
complementary static files (stylesheet, favicon, JavaScript):
620
@@ -645,9 +645,9 @@ parameter.
645
`@stylesheets`, `$my_uri` and `$home_link`, but you lose "dumb client"
646
access to your project .git dirs (described in "Single URL for gitweb and
647
for fetching" section). A possible workaround for the latter is the
648
-following: in your project root dir (e.g. '/pub/git') have the projects
649
-named *without* a .git extension (e.g. '/pub/git/project' instead of
650
-'/pub/git/project.git') and configure Apache as follows:
648
+following: in your project root dir (e.g. `/pub/git`) have the projects
649
+named *without* a .git extension (e.g. `/pub/git/project` instead of
650
+`/pub/git/project.git`) and configure Apache as follows:
651
----------------------------------------------------------------------------
652
<VirtualHost *:80>
653
ServerAlias git.example.com
@@ -681,7 +681,7 @@ cloned), while
681
will provide human-friendly gitweb access.
682
683
This solution is not 100% bulletproof, in the sense that if some project has
684
-a named ref (branch, tag) starting with 'git/', then paths such as
684
+a named ref (branch, tag) starting with `git/`, then paths such as
685
686
http://git.example.com/project/command/abranch..git/abranch
687
@@ -697,7 +697,7 @@ SEE ALSO
697
--------
698
linkgit:gitweb.conf[5], linkgit:git-instaweb[1]
699
700
-'gitweb/README', 'gitweb/INSTALL'
700
+`gitweb/README`, `gitweb/INSTALL`
701
702
GIT
703
---
Documentation/howto/setup-git-server-over-http.txt
+2
-2
@@ -244,8 +244,8 @@ Using a proxy:
244
--------------
245
246
If you have to access the WebDAV server from behind an HTTP(S) proxy,
247
-set the variable 'all_proxy' to 'http://proxy-host.com:port', or
248
-'http://login-on-proxy:passwd-on-proxy@proxy-host.com:port'. See 'man
247
+set the variable 'all_proxy' to `http://proxy-host.com:port`, or
248
+`http://login-on-proxy:passwd-on-proxy@proxy-host.com:port`. See 'man
249
curl' for details.
250
251
Documentation/revisions.txt
+2
-2
@@ -58,7 +58,7 @@ when you run `git merge`.
58
when you run `git cherry-pick`.
59
+
60
Note that any of the 'refs/*' cases above may come either from
61
-the '$GIT_DIR/refs' directory or from the '$GIT_DIR/packed-refs' file.
61
+the `$GIT_DIR/refs` directory or from the `$GIT_DIR/packed-refs` file.
62
While the ref name encoding is unspecified, UTF-8 is preferred as
63
some output processing may assume ref names in UTF-8.
64
@@ -108,7 +108,7 @@ some output processing may assume ref names in UTF-8.
108
`git push` were run while `branchname` was checked out (or the current
109
`HEAD` if no branchname is specified). Since our push destination is
110
in a remote repository, of course, we report the local tracking branch
111
- that corresponds to that branch (i.e., something in 'refs/remotes/').
111
+ that corresponds to that branch (i.e., something in `refs/remotes/`).
112
+
113
Here's an example to make it more clear:
114
+
Documentation/sequencer.txt
+1
-1
@@ -1,6 +1,6 @@
1
--continue::
2
Continue the operation in progress using the information in
3
- '.git/sequencer'. Can be used to continue after resolving
3
+ `.git/sequencer`. Can be used to continue after resolving
4
conflicts in a failed cherry-pick or revert.
5
6
--quit::