commit 376d4d523d69b4f587a937263f1d74b533d71864
from: Stefan Sperling
Multiple objects can be bundled in a pack file for better disk space efficiency and increased run-time performance. The pack file format introduces two additional types of objects:
@@ -151,18 +152,22 @@got(1), gotadmin(1), - deflate(3), SHA1(3), - got-worktree(5), got.conf(5)
+got(1), + gotadmin(1), + deflate(3), + SHA1(3), + got-worktree(5), + got.conf(5)
The particular set of disallowed characters in reference names is a consequence of design choices made for the command-line interface of - git(1). The same characters are disallowed by Got for - compatibility purposes. Got additionally prevents users from creating - reference names with a leading - (dash) character, because this is rarely - intended and not considered useful.
+ git(1). The same characters + are disallowed by Got for compatibility purposes. Got additionally prevents + users from creating reference names with a leading - (dash) character, + because this is rarely intended and not considered useful.June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |
got checkout
and is required to make changes to a
- Git repository with got(1).
+ Git repository with got(1).
A work tree stores the path to its Git repository, the name of a reference to the branch which files were checked out from, and the ID of a commit on this branch known as the @@ -57,11 +58,11 @@
When the file index is modified, it is read into memory in its entirety, modified in place, and written to a temporary file. This temporary file is then moved on top of the old file index with - rename(2). This ensures that no other processes see an - inconsistent file index which is in the process of being written.
+ rename(2). This ensures + that no other processes see an inconsistent file index which is in the + process of being written.Work tree meta data must only be modified while the work tree's lock file has been exclusively locked with - lockf(3).
+ lockf(3).Each work tree has a universal unique identifier. When a work tree is checked out or updated, this identifier is used to create a reference to the current base commit in the Git repository. The presence of this @@ -157,8 +160,9 @@
got(1), rename(2), - stat(2), umask(2), - lockf(3), git-repository(5), - got.conf(5)
+got(1), + rename(2), + stat(2), + umask(2), + lockf(3), + git-repository(5), + got.conf(5)
June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |
got
is a version control system which
stores the history of tracked files in a Git repository, as used by the Git
version control system. This repository format is described in
- git-repository(5).
got
is a “distributed”
version control system because every copy of a repository is writeable.
Modifications made to files can be synchronized between repositories at any
@@ -61,7 +62,7 @@
stored in a work
tree which can be placed at an arbitrary directory in the filesystem
hierarchy. The on-disk format of this work tree is described in
- got-worktree(5).
got
provides global and command-specific
options. Global options must precede the command name, and are as
follows:
The got import
command requires the
GOT_AUTHOR
environment variable to be set,
- unless an author has been configured in got.conf(5) or
- Git's user.name
and
- user.email
configuration settings can be
- obtained from the repository's .git/config file
- or from Git's global ~/.gitconfig configuration
- file.
user.name
and user.email
+ configuration settings can be obtained from the repository's
+ .git/config file or from Git's global
+ ~/.gitconfig configuration file.
The options for got import
are as
follows:
clone
@@ -155,13 +156,15 @@
The following protocol schemes are supported:
got clone
creates a remote repository
- entry in the got.conf(5) and
- config files of the cloned repository to store
- the repository-url and any
- branch or reference
+ entry in the got.conf(5) and config files of the
+ cloned repository to store the repository-url and
+ any branch or reference
arguments for future use by got fetch
or
- git-fetch(1).
The options for got clone
are as
follows:
-a
fetch-all-branches
in the cloned repository's
- got.conf(5) file for future use by
- got fetch
. If this option is not specified, a
- branch resolved via the remote repository's HEAD reference will be
- fetched. Cannot be used together with the -b
- option.fetch_all_branches
in the cloned repository's
+ got.conf(5) file
+ for future use by got fetch
. If this option is
+ not specified, a branch resolved via the remote repository's HEAD
+ reference will be fetched. Cannot be used together with the
+ -b
option.
-b
branchThe repository's got.conf(5) and
- config files will be set up with the
- “mirror” option enabled, such that
- got fetch
or git-fetch(1)
+
The repository's got.conf(5) and config files
+ will be set up with the “mirror” option enabled, such
+ that got fetch
or
+ git-fetch(1)
will write incoming changes directly to branches in the
“refs/heads/” reference namespace, rather than to
branches in the “refs/remotes/” namespace. This avoids
@@ -229,12 +234,14 @@
-q
-v
got clone
to print
debugging messages to standard error output. This option will be
- passed to ssh(1) if applicable. Multiple -v options
- increase the verbosity. The maximum is 3.-R
referencegot clone
.
+ obtained from the corresponding entry in
+ got.conf(5) or Git's
+ config file of the local repository, as created by
+ got clone
.
New changes will be stored in a separate pack file downloaded from the server. Optionally, separate pack files stored in the - repository can be combined with git-repack(1).
+ repository can be combined with git-repack(1).By default, branch references in the
“refs/remotes/” reference namespace will be updated to
point at the newly fetched commits. The got
@@ -301,10 +310,10 @@
-b
- option.-b
option.
-b
branch-q
-v
got fetch
to print
debugging messages to standard error output. The same option will be
- passed to ssh(1) if applicable. Multiple -v options
- increase the verbosity. The maximum is 3.-R
referenceWith -X
, the
remote-repository argument is mandatory and no
other options except -r
,
@@ -377,7 +388,8 @@
Only references are deleted. Any commit, tree, tag, and blob objects fetched from a remote repository will generally be stored in pack files and may be removed separately with - git-repack(1) and Git's garbage collector.
+ git-repack(1) + and Git's garbage collector.-s
option.
For compatibility with cvs(1) and
- git(1), got status
reads
- glob(7) patterns from
- .cvsignore and
- .gitignore files in each traversed directory and
- will not display unversioned files which match these patterns. As an
- extension to glob(7) matching rules,
- got status
supports consecutive asterisks,
- “**”, which will match an arbitrary amount of directories.
- Unlike cvs(1), got status
only
- supports a single ignore pattern per line. Unlike
- git(1), got status
does not
- support negated ignore patterns prefixed with “!”, and
- gives no special significance to the location of path component
- separators, “/”, in a pattern.
For compatibility with cvs(1) and git(1),
+ got status
reads glob(7) patterns from .cvsignore
+ and .gitignore files in each traversed directory
+ and will not display unversioned files which match these patterns. As an
+ extension to glob(7)
+ matching rules, got status
supports consecutive
+ asterisks, “**”, which will match an arbitrary amount of
+ directories. Unlike cvs(1), got status
only supports a single
+ ignore pattern per line. Unlike git(1), got status
does not support
+ negated ignore patterns prefixed with “!”, and gives no
+ special significance to the location of path component separators,
+ “/”, in a pattern.
log
[-b
] [-c
@@ -755,7 +768,8 @@
patches will be matched if -p
is specified.
File paths changed by a commit will be matched if
-P
is specified. Regular expression syntax is
- documented in re_format(7).
+ documented in re_format(7).
-r
repository-path-c
commit]
[-m
message]
[-r
repository-path]
- [-l
] name
+ [-l
] [-s
+ signer-id] [-v
]
+ [-V
] name
Tags are managed via references which live in the
“refs/tags/” reference namespace. The got
@@ -1148,8 +1164,41 @@
repository path associated with this work tree.
-l
-s
+ signer-idFor SSH-based signatures, signer-id
+ is the path to a file which may refer to either a private SSH key,
+ or a public SSH key with the private half available via
+ ssh-agent(1).
+ got tag
will sign the tag object by invoking
+ ssh-keygen(1)
+ with the -Y
sign
+ command, using the signature namespace “git” for
+ compatibility with git(1).
-v
-V
got tag
verifies SSH-based
+ signatures by invoking ssh-keygen(1) with the options -Y
+ verify -f
+ allowed_signers. A path to the
+ allowed_signers file must be set in
+ got.conf(5),
+ otherwise verification is impossible.
By design, the got tag
command will
not delete tags or change existing tags. If a tag must be deleted, the
@@ -1197,7 +1246,7 @@
got remove
will refuse to run if a specified
path is a directory.-s
+ -s
status-codesThe patch must be in the unified diff format as produced by
- got diff
, git-diff(1), or by
- diff(1) and cvs(1) diff when invoked
- with their -u
options. If no
- patchfile argument is provided, read unified diff
- data from standard input instead.
got diff
, git-diff(1), or by diff(1) and cvs(1) diff when invoked with their -u
+ options. If no patchfile argument is provided,
+ read unified diff data from standard input instead.
If the patchfile contains multiple patches, then attempt to apply each of them in sequence.
Show the status of each affected file, using the following @@ -1243,6 +1293,14 @@
-p
option is not used, ‘a/’ and
‘b/’ path prefixes generated by
- git-diff(1) will be recognized and stripped
- automatically.-R
The got commit
command requires the
GOT_AUTHOR
environment variable to be set,
- unless an author has been configured in got.conf(5) or
- Git's user.name
and
- user.email
configuration settings can be
- obtained from the repository's .git/config file
- or from Git's global ~/.gitconfig configuration
- file.
user.name
and user.email
+ configuration settings can be obtained from the repository's
+ .git/config file or from Git's global
+ ~/.gitconfig configuration file.
The options for got commit
are as
follows:
got clone
.
+ obtained from the corresponding entry in
+ got.conf(5) or Git's
+ config file of the local repository, as created by
+ got clone
.
All objects corresponding to new changes will be written to a
temporary pack file which is then uploaded to the server. Upon success,
references in the “refs/remotes/” reference namespace of
@@ -1542,12 +1601,14 @@
together with the -t
option.
-q
-v
-v
got send
to print
debugging messages to standard error output. The same option will be
- passed to ssh(1) if applicable. Multiple -v options
- increase the verbosity. The maximum is 3.cherrypick
@@ -2396,7 +2457,8 @@
info
[path ...]The work tree to use is resolved implicitly by walking upwards from the current working directory.
If one or more path arguments are
@@ -2415,29 +2477,31 @@
and got import
, for example:
“Flan Hacker
<flan_hacker@openbsd.org>”.
- Because git(1) may fail to parse commits without an
- email address in author data, got
attempts to
- reject GOT_AUTHOR
environment variables with a
- missing email address.
+ Because git(1) may fail to
+ parse commits without an email address in author data,
+ got
attempts to reject
+ GOT_AUTHOR
environment variables with a missing
+ email address.
GOT_AUTHOR will be overridden by
- configuration settings in
got.conf(5) or by
- Git's user.name
and
- user.email
configuration settings in the
+ configuration settings in got.conf(5) or by Git's user.name
+ and user.email
configuration settings in the
repository's .git/config file. The
user.name
and user.email
configuration settings contained in Git's global
~/.gitconfig configuration file will only be
- used if neither got.conf(5) nor the
- GOT_AUTHOR
environment variable provide author
- information.
GOT_AUTHOR
+ environment variable provide author information.
VISUAL
,
EDITOR
got commit
,
got histedit
, got import
,
or got tag
. If not set, the
- ed(1) text editor will be spawned in order to give
- ed(1) the attention it deserves.GOT_LOG_DEFAULT_LIMIT
got log
. If set to zero, the limit is unbounded.
@@ -2450,17 +2514,20 @@
got
. If
- present, a got.conf(5) configuration file located in the
- root directory of a Git repository supersedes any relevant settings in
- Git's config file.
+ present, a got.conf(5)
+ configuration file located in the root directory of a Git repository
+ supersedes any relevant settings in Git's config
+ file.
got
.
- If present, a got.conf(5) configuration file in the
- .got meta-data directory of a work tree supersedes
- any relevant settings in the repository's got.conf(5)
- configuration file and Git's config file.Enable tab-completion of got
command names
- in ksh(1):
$ set -A complete_got_1 -- $(got -h
2>&1 | sed -n s/commands://p)
$ cd /var/git/
$ got clone
ssh://git@github.com/openbsd/src.git
Use of HTTP URLs currently requires git(1):
+Use of HTTP URLs currently requires git(1):
$ cd /var/git/
$ git clone --bare
@@ -2539,7 +2607,8 @@
$ got log -p -l 3
As above, but display changes in the order in which
- patch(1) could apply them in sequence:
+ patch(1) could apply them in
+ sequence:
$ got log -p -l 3 -R
In a work tree or a git repository directory, log the history of a
@@ -2603,8 +2672,8 @@
$ cd /usr/src
$ got fetch
In a repository created with a HTTP URL and git
- clone --bare
the git-fetch(1) command must be used
- instead:
+ clone --bare
the git-fetch(1) command must be used instead:
$ cd /var/git/src.git
$ git fetch origin
@@ -2655,9 +2724,9 @@
$ cd /var/git/repo
$ git config remote.origin.mirror
false
-Alternatively, the following git-fetch(1)
- configuration item can be added manually to the Git repository's
- config file:
+Alternatively, the following git-fetch(1) configuration item can be added manually to the
+ Git repository's config file:
[remote
"origin"]
@@ -2671,9 +2740,9 @@
got branch
. Branches in the
“refs/remotes/origin” namespace can now be updated with
incoming changes from the remote repository with got
- fetch
or git-fetch(1) without extra command line
- arguments. Newly fetched changes can be examined with got
- log
.
+ fetch
or git-fetch(1) without extra command line arguments. Newly fetched
+ changes can be examined with got log
.
Display changes on the remote repository's version of the
“master” branch, as of the last time got
fetch
was run:
$ got send -b master
origin
If the remote repository requires the HTTPS protocol, the - git-push(1) command must be used instead:
+ git-push(1) command must + be used instead:$ cd /var/git/src.git
$ git push origin master
gotadmin(1), tog(1), - git-repository(5), got-worktree(5), - got.conf(5)
+gotadmin(1), + tog(1), + git-repository(5), + got-worktree(5), + got.conf(5)
got
is a work-in-progress and some
features remain to be implemented.
At present, the user has to fall back on git(1) - to perform some tasks. In particular:
+At present, the user has to fall back on + git(1) to perform some tasks. + In particular:
got
will not automatically merge changes to new
- locations and git(1) will usually produce better
- results.June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |
got.conf
is the run-time configuration
- file for got(1).
got.conf
may be present in the root
directory of a Git repository for repository-wide settings, or in the
.got meta-data directory of a work tree to override
- repository-wide settings for got(1) commands executed
- within this work tree.
The file format is line-based, with one configuration directive per line. Any lines beginning with a ‘#’ are treated as comments and ignored.
@@ -55,10 +55,34 @@ commit andgot import
when operating on
this repository. Author information specified here overrides the
GOT_AUTHOR
environment variable.
- Because git(1) may fail to parse commits - without an email address in author data, got(1) - attempts to reject author information with a missing email address.
+Because git(1) + may fail to parse commits without an email address in author data, + got(1) attempts to reject + author information with a missing email address.
+allowed_signers
+ pathgot tag
-V
. The format of
+ the "allowed signers" file is documented in the ALLOWED SIGNERS
+ section of ssh-keygen(1).
+ Verification of SSH-based signatures is impossible unless the
+ allowed_signers
option is set in
+ got.conf
.
revoked_signers
+ pathgot tag
-V
. Revoked
+ identities are no longer considered trustworthy and verification of
+ relevant signatures will fail.remote
name {...}protocol
will be
- used.
+ services(5) for
+ details. If not specified, the default port of the specified
+ protocol
will be used.
branch
{branch ...}got fetch
@@ -113,7 +137,7 @@
be overridden at the got fetch
and
got send
command lines with the
-b
option.fetch-all-branches
+ fetch_all_branches
yes | nogot fetch
will
fetch all branches from the remote repository by default. If enabled,
@@ -133,7 +157,7 @@
“refs/got/” namespace. In any case, references in the
“refs/tags/” namespace will always be fetched and mapped
directly to local references in the same namespace.mirror-references
+ mirror_references
yes | nogot
fetch
when updating references.
@@ -214,7 +238,7 @@
repository "openbsd/src"
server git@github.com
protocol git+ssh
- mirror-references yes
+ mirror_references yes
}
Fetch changes via the Git protocol and send changes via the SSH @@ -243,16 +267,17 @@
got.conf
located in the
.got meta-data directory of a
- got(1) work tree supersedes any relevant settings in the
- repository's got.conf
configuration file and Git's
- config file.got.conf
+ configuration file and Git's config file.
June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |
gotadmin
is the repository maintenance
- tool for the got(1) version control system.
got(1) stores the history of tracked files in a
- Git repository, as used by the Git version control system.
- gotadmin
provides commands for inspecting and
- manipulating the on-disk state of Git repositories. The repository format is
- described in git-repository(5).
got(1) stores the
+ history of tracked files in a Git repository, as used by the Git version
+ control system. gotadmin
provides commands for
+ inspecting and manipulating the on-disk state of Git repositories. The
+ repository format is described in git-repository(5).
gotadmin
provides global and
command-specific options. Global options must precede the command name, and
are as follows:
info
[-r
repository-path]The options for gotadmin info
are as
follows:
pack
@@ -112,8 +116,9 @@
repository-path-x
referenceA pack index is required for using the corresponding pack file
- with got(1). Usually, a pack index will be created by
- commands such as gotadmin pack
or
- got fetch
as part of regular operation. The
- gotadmin indexpack
command may be used to
- recover from a corrupt or missing index. A given pack file will always
- yield the same bit-identical index.
gotadmin
+ pack
or got fetch
as part of regular
+ operation. The gotadmin indexpack
command may be
+ used to recover from a corrupt or missing index. A given pack file will
+ always yield the same bit-identical index.
The provided packfile-path must be located within the objects/pack/ directory of the repository and should end in .pack. The @@ -252,8 +257,9 @@ repository-path
-q
got(1), tog(1), - git-repository(5), got.conf(5)
+got(1), + tog(1), + git-repository(5), + got.conf(5)
gotadmin
is a work-in-progress and some
features remain to be implemented.
At present, the user has to fall back on git(1) - to perform some tasks. In particular:
+At present, the user has to fall back on + git(1) to perform some tasks. + In particular:
Disk space savings reported by gotadmin
cleanup
will be misleading if the repository contains object files
that were hard-linked from another repository. Such hard-links will be
- created by certain git(1) commands. By itself,
- got(1) will never create hard-linked object files.
June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |
gotweb
provides a web interface allowing
Git repository contents to be viewed with a web browser.
gotweb
is a CGI program based on
- got(1) and kcgi(3) which is intended to
- run in a chroot(2) environment in
- /var/www. The program has been designed to work out
- of the box with the httpd(8) web server in conjunction
- with slowcgi(8).
Enabling gotweb
requires the following
steps:
gotweb
as a CGI program with
- slowcgi(8). The
- EXAMPLES section below contains an
- appropriate configuration file sample.gotweb
+ as a CGI program with slowcgi(8). The EXAMPLES section
+ below contains an appropriate configuration file sample.# rcctl enable httpd slowcgi @@ -69,19 +71,21 @@
gotweb
can
- be configured via the gotweb.conf(5) configuration
- file.gotweb
is
+ the user ID of the httpd(8) server. The default location for repositories published by
+ gotweb
is
/var/www/got/public.gotweb
should be kept
up-to-date with a mechanism such as got fetch
,
- git-fetch(1), or rsync(1), scheduled
- by cron(8).gotweb
. This location can be adjusted in the
- gotweb.conf(5) configuration file.gotweb
CGI program, statically linked for use
- in a chroot(2) environment.gotweb
.gotweb
to read Git
- repositories.gotweb
to read Git repositories.gotweb
.got(1), kcgi(3), - git-repository(5), gotweb.conf(5), - httpd(8), slowcgi(8)
+got(1), + kcgi(3), + git-repository(5), + gotweb.conf(5), + httpd(8), + slowcgi(8)
June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |
gotweb.conf
is the run-time configuration
- file for gotweb(8).
The file format is line-based, with one configuration directive per line. Any lines beginning with a ‘#’ are treated as comments and ignored.
Paths mentioned in gotweb.conf
must be
relative to /var/www, the
- chroot(2) environment of httpd(8).
got_max_repos
numbergot_max_repos_display
numbergot_repos_path
pathgot_show_repo_owner
on | off[gotweb] owner = "Your Name"@@ -115,7 +118,8 @@ owner = "Your Name"
These are the currently configurable items for - gotweb(8) with their default values.
+ gotweb(8) with their + default values.# @@ -156,12 +160,13 @@ got_logo_url "https://gameoftrees.org"SEE ALSO
- +
June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |
tog
is an interactive read-only browser
for Git repositories. This repository format is described in
- git-repository(5).
tog
supports several types of views which
display repository data:
tog
provides global and command-specific
- key bindings and options. The global key bindings are:
tog
will echo digits to the screen when count
+ modifiers are entered, and complete the sequence upon input of the first
+ non-numeric character. Count modifiers can be aborted by entering an
+ unmapped key. Once a compound command is executed, the operation can be
+ cancelled with C-g
or
+ Backspace
. The global key bindings are:
Q
tog
.Tab
f
F
tog
will automatically use split-screen views if
the size of the terminal window is sufficiently large.This command is also executed if no explicit command is specified.
The key bindings for tog log
are as
- follows:
Down-arrow,
j, >, Full stop, Ctrl-n
Up-arrow,
k, <, Comma, Ctrl-p
Right-arrow,
l
Left-arrow,
h
$
0
Page-down,
- Ctrl+f
Page-up,
- Ctrl+b
Ctrl+d,
d
Ctrl+u,
u
Home,
g
Backspace
.Enter,
- Space
C-g
or
+ Backspace
.
+ Enter
diff
view showing file changes made in
the currently selected commit.t
n
Backspace
key is pressed.C-g
or the Backspace
+ key is pressed.N
Backspace
key is pressed.C-g
or the Backspace
+ key is pressed.Ctrl+l
log
view with new commits found in
the repository.diff
@@ -229,39 +247,43 @@
abbreviated hash argument will be expanded to a full SHA1 hash
automatically, provided the abbreviation is unique.
The key bindings for tog diff
are as
- follows:
a
Down-arrow,
j, Ctrl-n
Up-arrow,
k, Ctrl-p
Right-arrow,
l
Left-arrow,
h
$
0
Page-down,
- Space, Ctrl+f
Page-up,
- Ctrl+b
Ctrl+d,
d
Ctrl+u,
u
Home,
g
[
]
<,
Comma
diff
view was opened via the
- log
view, move to the previous (younger)
- commit.log
view, move to the Nth previous (younger)
+ commit (default: 1).
>,
Full stop
diff
view was opened via the
- log
view, move to the next (older)
- commit.log
view, move to the Nth next (older) commit
+ (default: 1).
/
n
N
w
A
blame
view.The options for tog diff
are as
follows:
-w
The key bindings for tog blame
are as
- follows:
Down-arrow,
j, Ctrl-n
Up-arrow,
k, Ctrl-p
Right-arrow,
l
Left-arrow,
h
$
0
Page-down,
- Space, Ctrl+f
Page-up,
- Ctrl+b
Ctrl+d,
d
Ctrl+u,
u
Home,
g
End,
G
Enter
Enter
diff
view for the currently selected
line's commit.b
c
blame
view with the version of the
file as found in the currently selected line's commit.p
blame
view with the version of the
file as found in the parent commit of the currently selected line's
commit.B
C
blame
view with the previously
blamed commit./
n
N
A
diff
view.The options for tog blame
are as
follows:
-c
+ -c
committree
@@ -426,33 +466,33 @@
Symbolic link entries are also annotated with the target path of the link.
The key bindings for tog tree
are as
- follows:
Down-arrow,
j, Ctrl-n
Up-arrow,
k, Ctrl-p
Page-down,
- Ctrl+f
Page-up,
- Ctrl+b
Ctrl+d,
d
Ctrl+u,
u
Home,
g
End,
G
Enter
Enter
blame
view for the currently selected
file.tree
view for arbitrary branches and
tags.
Backspace
i
tree
view.n
N
The options for tog tree
are as
follows:
-c
+ -c
commitref
[-r
repository-path]The key bindings for tog ref
are as
- follows:
Down-arrow,
j, Ctrl-n
Up-arrow,
k, Ctrl-p
Page-down,
- Ctrl+f
Page-up,
- Ctrl+b
Ctrl+d,
d
Ctrl+u,
u
Home,
g
End,
G
Enter
Enter
log
view which begins traversing
history at the commit resolved via the currently selected
reference.n
N
Ctrl+l
ref
view.TOG_DIFF_ALGORITHM
tog
.
+ Supported diff algorithms are Myers (quick and dirty) and Patience (slow
+ and tidy). Valid values for TOG_DIFF_ALGORITHM
are
+ “patience” and “myers”. If unset, the Myers
+ diff algorithm will be used by default.TOG_VIEW_SPLIT_MODE
tog
will use vertical or
+ horizontal split for split-screen views. If set to “h” then
+ split-screen views will be split horizontally. Otherwise, split-screen
+ views will be split vertically.TOG_COLORS
tog
shows colorized output if this variable is set
to a non-empty value. The default color scheme can be modified by setting
@@ -642,8 +698,9 @@
June 18, 2022 | +July 4, 2022 | OpenBSD 7.1 |