commit - 7b15f394cc48dec0639dc34a1cf939a4f20f08d3
commit + bd0bf38778e2381d5951ab5d7f7411ff62d93e4b
blob - 2ebd0dec63ec9e12b29d2b40f7087f38a3de22cc
blob + 748836b22229c138b54386f342915d2fbbf72a9c
--- git-repository.5.html
+++ git-repository.5.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - d65d0897c40fd6083dd62bfe743e91c90dbfefdb
blob + 82452f07891253bdba9953ee86ec1838003d2cdb
--- gitwrapper.1.html
+++ gitwrapper.1.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 5f0f68adc6185e16646fb059b732111ff68d0c6a
blob + 9f112b2eef1ea7fb9612b912eb4072238b3c3435
--- got-worktree.5.html
+++ got-worktree.5.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 62a7177d76f13697ccc47eba343683c7f051d3c5
blob + 1f30ef1e080b44cab9ef78f963a4c616df9a6f75
--- got.1.html
+++ got.1.html
<a class="Xr" aria-label="git-daemon, section 1">git-daemon(1)</a>
server. Use of this protocol is discouraged since it supports neither
authentication nor encryption.</dd>
- <dt>git+ssh</dt>
+ <dt>ssh</dt>
<dd>The Git protocol wrapped in an authenticated and encrypted
<a class="Xr" aria-label="ssh, section 1">ssh(1)</a> tunnel. With this
protocol the hostname may contain an embedded username for
<a class="Xr" aria-label="ssh, section 1">ssh(1)</a> to use:
<a class="Mt" href="mailto:user@hostname">user@hostname</a></dd>
- <dt>ssh</dt>
- <dd>Short alias for git+ssh.</dd>
+ <dt>http</dt>
+ <dd>The “smart” Git HTTP protocol. Not compatible with
+ servers using the “dumb” Git HTTP protocol.
+ <p class="Pp">The “smart” Git HTTP protocol is supported
+ by <code class="Cm">got clone</code> and <code class="Cm">got
+ fetch</code>, but not by <code class="Cm">got send</code>. Sending
+ from a repository cloned over HTTP will require use of the
+ <code class="Ic">send</code> directive in
+ <a class="Xr" aria-label="got.conf, section 5">got.conf(5)</a> to
+ ensure that the “ssh://” protocol will be used by
+ <code class="Cm">got send</code>.</p>
+ <p class="Pp">Use of this protocol is discouraged since it supports
+ neither authentication nor encryption.</p>
+ </dd>
+ <dt>https</dt>
+ <dd>The “smart” Git HTTP protocol wrapped in SSL/TLS.</dd>
</dl>
<p class="Pp">Objects in the cloned repository are stored in a pack file
which is downloaded from the server. This pack file will then be indexed
<td>file was modified after having been staged for addition</td>
</tr>
</table>
+ <p class="Pp">If the work tree contains the results of an interrupted
+ <code class="Cm">got rebase</code>, <code class="Cm">got
+ histedit</code>, or <code class="Cm">got merge</code> operation then
+ display a message which shows the branches involved.</p>
<p class="Pp">The options for <code class="Cm">got status</code> are as
follows:</p>
<dl class="Bl-tag">
“/”, in a pattern.</p>
</dd>
<dt id="log"><a class="permalink" href="#log"><code class="Cm">log</code></a>
- [<code class="Fl">-bdPpRs</code>] [<code class="Fl">-C</code>
+ [<code class="Fl">-bdPpRst</code>] [<code class="Fl">-C</code>
<var class="Ar">number</var>] [<code class="Fl">-c</code>
<var class="Ar">commit</var>] [<code class="Fl">-l</code>
<var class="Ar">N</var>] [<code class="Fl">-r</code>
<dd>Display a short one-line summary of each commit, instead of the
default history format. Cannot be used together with the
<code class="Fl">-p</code> or <code class="Fl">-P</code> option.</dd>
+ <dt id="t~2"><a class="permalink" href="#t~2"><code class="Fl">-t</code></a></dt>
+ <dd>Display commits in topological order. This option has no effect
+ without the <code class="Fl">-b</code> option because a linear history
+ is sorted in topological order by definition. Topological sorting is
+ disabled by default because the present implementation requires that
+ commit history is fully traversed before any output can be shown.</dd>
<dt id="x"><a class="permalink" href="#x"><code class="Fl">-x</code></a>
<var class="Ar">commit</var></dt>
<dd>Stop traversing commit history immediately after the specified
loops between references when this option is used. Cannot be used
together with any other options except
<code class="Fl">-r</code>.</dd>
- <dt id="t~2"><a class="permalink" href="#t~2"><code class="Fl">-t</code></a></dt>
+ <dt id="t~3"><a class="permalink" href="#t~3"><code class="Fl">-t</code></a></dt>
<dd>Sort listed references by modification time (most recently modified
first) instead of sorting by lexicographical order. Use of this option
requires the <code class="Fl">-l</code> option to be used as
repository is located at or above the current working directory. If
this directory is a <code class="Nm">got</code> work tree, use the
repository path associated with this work tree.</dd>
- <dt id="t~3"><a class="permalink" href="#t~3"><code class="Fl">-t</code></a></dt>
+ <dt id="t~4"><a class="permalink" href="#t~4"><code class="Fl">-t</code></a></dt>
<dd>Sort listed branches by modification time (most recently modified
first) instead of sorting by lexicographical order. Branches in the
“refs/heads/” reference namespace are listed before
<code class="Fl">-T</code> option is equivalent to listing all tags
with multiple <code class="Fl">-t</code> options. Cannot be used
together with the <code class="Fl">-t</code> option.</dd>
- <dt id="t~4"><a class="permalink" href="#t~4"><code class="Fl">-t</code></a>
+ <dt id="t~5"><a class="permalink" href="#t~5"><code class="Fl">-t</code></a>
<var class="Ar">tag</var></dt>
<dd>Send the specified <var class="Ar">tag</var> from the local
repository's “refs/tags/” reference namespace, in
</dl>
</dd>
<dt id="sg"><a class="permalink" href="#stage"><code class="Cm" id="stage">stage</code></a>
- [<code class="Fl">-lpS</code>] [<code class="Fl">-F</code>
+ [<code class="Fl">-lpRS</code>] [<code class="Fl">-F</code>
<var class="Ar">response-script</var>] [<var class="Ar">path ...</var>]</dt>
<dd>
<div class="Bd Bd-indent"><code class="Li">(alias:
individual patches derived from the modified file content can be
staged. Files in added or deleted status may only be staged or
rejected in their entirety.</dd>
+ <dt id="R~9"><a class="permalink" href="#R~9"><code class="Fl">-R</code></a></dt>
+ <dd>Permit recursion into directories. If this option is not specified,
+ <code class="Cm">got stage</code> will refuse to run if a specified
+ <var class="Ar">path</var> is a directory.</dd>
<dt id="S~4"><a class="permalink" href="#S~4"><code class="Fl">-S</code></a></dt>
<dd>Allow staging of symbolic links which point outside of the path space
that is under version control. By default, <code class="Cm">got
necessary.</p>
</dd>
<dt id="ug"><a class="permalink" href="#unstage"><code class="Cm" id="unstage">unstage</code></a>
- [<code class="Fl">-p</code>] [<code class="Fl">-F</code>
+ [<code class="Fl">-pR</code>] [<code class="Fl">-F</code>
<var class="Ar">response-script</var>] [<var class="Ar">path ...</var>]</dt>
<dd>
<div class="Bd Bd-indent"><code class="Li">(alias:
If a file is staged in modified status, individual patches derived
from the staged file content can be unstaged. Files staged in added or
deleted status may only be unstaged in their entirety.</dd>
+ <dt id="R~10"><a class="permalink" href="#R~10"><code class="Fl">-R</code></a></dt>
+ <dd>Permit recursion into directories. If this option is not specified,
+ <code class="Cm">got unstage</code> will refuse to run if a specified
+ <var class="Ar">path</var> is a directory.</dd>
</dl>
</dd>
<dt id="cat"><a class="permalink" href="#cat"><code class="Cm">cat</code></a>
anonymous access via SSH. Such sites will require an account to be created,
and a public SSH key to be uploaded to this account, before repository
access via ssh:// URLs will work.</p>
-<p class="Pp">Use of HTTP URLs currently requires <a class="Xr" aria-label="git,
- section 1">git(1)</a>:</p>
+<p class="Pp">Most sites offer anonymous repository access via HTTPS:</p>
<p class="Pp"></p>
<div class="Bd Bd-indent"><code class="Li">$ cd /var/git/</code></div>
-<div class="Bd Bd-indent"><code class="Li">$ git clone --bare
+<div class="Bd Bd-indent"><code class="Li">$ got clone
https://github.com/openbsd/src.git</code></div>
<p class="Pp">Alternatively, for quick and dirty local testing of
<code class="Nm">got</code> a new Git repository could be created and
<p class="Pp"></p>
<div class="Bd Bd-indent"><code class="Li">$ cd /usr/src</code></div>
<div class="Bd Bd-indent"><code class="Li">$ got fetch</code></div>
-<p class="Pp">In a repository created with a HTTP URL and <code class="Cm">git
- clone --bare</code> the <a class="Xr" aria-label="git-fetch, section
- 1">git-fetch(1)</a> command must be used instead:</p>
-<p class="Pp"></p>
-<div class="Bd Bd-indent"><code class="Li">$ cd /var/git/src.git</code></div>
-<div class="Bd Bd-indent"><code class="Li">$ git fetch origin
- master:refs/remotes/origin/master</code></div>
<p class="Pp">Rebase the local “master” branch to merge the new
changes that are now visible on the “origin/master”
branch:</p>
<a class="Xr" aria-label="git, section 1">git(1)</a> to perform some tasks.
In particular:</p>
<ul class="Bl-bullet">
- <li>Reading from remote repositories over HTTP or HTTPS protocols requires
- <a class="Xr" aria-label="git-clone, section 1">git-clone(1)</a> and
- <a class="Xr" aria-label="git-fetch, section 1">git-fetch(1)</a>.</li>
<li>Writing to remote repositories over HTTP or HTTPS protocols requires
<a class="Xr" aria-label="git-push, section 1">git-push(1)</a>.</li>
<li>The creation of merge commits with more than two parent commits requires
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - abf21812acf06903ae98b7f6185dfbb5fd5faea0
blob + 1917a233a6eb9eee6d95a52e39bfc9f9c1e693e3
--- got.conf.5.html
+++ got.conf.5.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 64a934e2426369f0c2dc3b0cbfee24f5e2971252
blob + 3908702f5fa21b3db0aaa5e2411ce87751245062
--- gotadmin.1.html
+++ gotadmin.1.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 8a107c269f9a4f65962e971554b2f6a60c16a1c5
blob + dd544668c4959201fb0376ff2340a043b005e0d9
--- gotctl.8.html
+++ gotctl.8.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 15a37fbb779dce66cf83bc7ee8e8d84da6ca74a5
blob + 934c1d4fe17f4b57a6e53a0d6b195b06cb45a367
--- gotd.8.html
+++ gotd.8.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 30a53bb588f951cd2c2246bc9e49a9861e713af3
blob + 10d040b23b01c6dd5e2dbd9b635a4689c9b3f97a
--- gotd.conf.5.html
+++ gotd.conf.5.html
<code class="Nm">gotd.conf</code>. These namespaces are always protected
and even attempts to create new references in these namespaces will
always be denied.</p>
+ </dd>
+ <dt id="notify"><a class="permalink" href="#notify"><code class="Ic">notify</code></a>
+ {<var class="Ar">...</var>}</dt>
+ <dd>The <code class="Ic">notify</code> directive enables notifications about
+ new commits or tags added to the repository.
+ <p class="Pp">Notifications via email require an SMTP daemon which accepts
+ mail for forwarding without requiring client authentication or
+ encryption. On <span class="Ux">OpenBSD</span> the
+ <a class="Xr" aria-label="smtpd, section 8">smtpd(8)</a> daemon can be
+ used for this purpose. The default content of email notifications looks
+ similar to the output of the <code class="Cm">got log -d</code>
+ command.</p>
+ <p class="Pp">Notifications via HTTP require a HTTP or HTTPS server which is
+ accepting POST requests with or without HTTP Basic authentication.
+ Depending on the use case a custom server-side CGI script may be
+ required for the processing of notifications. HTTP notifications can
+ achieve functionality similar to Git's server-side post-receive hook
+ script with <a class="Xr" aria-label="gotd, section 8">gotd(8)</a> by
+ triggering arbitrary post-commit actions via the HTTP server.</p>
+ <p class="Pp">The <code class="Ic">notify</code> directive expects
+ parameters which must be enclosed in curly braces. The available
+ parameters are as follows:</p>
+ <dl class="Bl-tag">
+ <dt id="branch~3"><a class="permalink" href="#branch~3"><code class="Ic">branch</code></a>
+ <var class="Ar">name</var></dt>
+ <dd>Send notifications about commits to the named branch. The
+ <var class="Ar">name</var> will be looked up in the
+ “refs/heads/” reference namespace. This directive may be
+ specified multiple times to build a list of branches to send
+ notifications for. If neither a <code class="Ic">branch</code> nor a
+ <code class="Ic">reference namespace</code> are specified then changes
+ to any reference will trigger notifications.</dd>
+ <dt id="reference"><a class="permalink" href="#reference"><code class="Ic">reference</code></a>
+ <code class="Ic">namespace</code> <var class="Ar">namespace</var></dt>
+ <dd>Send notifications about commits or tags within a reference namespace.
+ This directive may be specified multiple times to build a list of
+ namespaces to send notifications for. If neither a
+ <code class="Ic">branch</code> nor a <code class="Ic">reference
+ namespace</code> are specified then changes to any reference will
+ trigger notifications.</dd>
+ <dt id="email"><a class="permalink" href="#email"><code class="Ic">email</code></a>
+ [<code class="Ic">from</code> <var class="Ar">sender</var>]
+ <code class="Ic">to</code> <var class="Ar">recipient</var>
+ [<code class="Ic">reply to</code> <var class="Ar">responder</var>]
+ [<code class="Ic">relay</code> <var class="Ar">hostname</var>
+ [<code class="Ic">port</code> <var class="Ar">port</var>]]</dt>
+ <dd>Send notifications via email to the specified
+ <var class="Ar">recipient</var>. This directive may be specified
+ multiple times to build a list of recipients to send notifications to.
+ <p class="Pp">The <var class="Ar">recipient</var> must be an email
+ addresses that accepts mail. The <var class="Ar">sender</var> will
+ be used as the From address. If not specified, the sender defaults
+ to an email address composed of the user account running
+ <a class="Xr" aria-label="gotd, section 8">gotd(8)</a> and the local
+ hostname.</p>
+ <p class="Pp">If a <var class="Ar">responder</var> is specified via the
+ <code class="Ic">reply to</code> directive, the
+ <var class="Ar">responder</var> will be used as the Reply-to
+ address. Setting the Reply-to header can be useful if replies should
+ go to a mailing list instead of the <var class="Ar">sender</var>,
+ for example.</p>
+ <p class="Pp">By default, mail will be sent to the SMTP server listening
+ on the loopback address 127.0.0.1 on port 25. The
+ <code class="Ic">relay</code> and <code class="Ic">port</code>
+ directives can be used to specify a different SMTP server address
+ and port.</p>
+ </dd>
+ <dt id="url"><a class="permalink" href="#url"><code class="Ic">url</code></a>
+ <var class="Ar">URL</var> [<code class="Ic">user</code>
+ <var class="Ar">user</var> <code class="Ic">password</code>
+ <var class="Ar">password</var> [<code class="Ic">insecure</code>]]</dt>
+ <dd>Send notifications via HTTP. This directive may be specified multiple
+ times to build a list of HTTP servers to send notifications to.
+ <p class="Pp">The notification will be sent as a POST request to the
+ given <var class="Ar">URL</var>, which must be a valid HTTP URL and
+ begin with either “http://” or
+ “https://”. If HTTPS is used, sending of notifications
+ will only succeed if no TLS errors occur.</p>
+ <p class="Pp">The optional <code class="Ic">user</code> and
+ <code class="Ic">password</code> directives enable HTTP Basic
+ authentication. If used, both a <var class="Ar">user</var> and a
+ <var class="Ar">password</var> must be specified. The
+ <var class="Ar">password</var> must not be an empty string. Unless
+ the <code class="Ic">insecure</code> option is specified the
+ notification target <var class="Ar">URL</var> must be a
+ “https://” URL to avoid leaking of authentication
+ credentials.</p>
+ <p class="Pp">The request body contains a JSON object with a
+ “notifications” property containing an array of
+ notification objects. Each notification object has a
+ ‘type’ property. Depending on the type, each
+ notification object has different fields. The types are:</p>
+ <dl class="Bl-tag">
+ <dt id="commit"><a class="permalink" href="#commit"><code class="Dv">commit</code></a></dt>
+ <dd>The commit notification object has the following fields. Except
+ where noted, all are optional.
+ <dl class="Bl-tag">
+ <dt id="short"><a class="permalink" href="#short"><code class="Dv">short</code></a></dt>
+ <dd>Boolean, indicates whether the object has all the fields set.
+ When several commits are batched in a single send operation,
+ not all of the fields are available for each commit
+ object.</dd>
+ <dt id="repo"><a class="permalink" href="#repo"><code class="Dv">repo</code></a></dt>
+ <dd>The repository name as string.</dd>
+ <dt id="id"><a class="permalink" href="#id"><code class="Dv">id</code></a></dt>
+ <dd>The commit ID as string, may be abbreviated.</dd>
+ <dt id="committer"><a class="permalink" href="#committer"><code class="Dv">committer</code></a></dt>
+ <dd>An object with the committer information with the following
+ fields:
+ <p class="Pp"></p>
+ <dl class="Bl-tag Bl-compact">
+ <dt id="full"><a class="permalink" href="#full"><code class="Dv">full</code></a></dt>
+ <dd>Committer's full name.</dd>
+ <dt id="name"><a class="permalink" href="#name"><code class="Dv">name</code></a></dt>
+ <dd>Committer's name.</dd>
+ <dt id="mail"><a class="permalink" href="#mail"><code class="Dv">mail</code></a></dt>
+ <dd>Committer's mail address.</dd>
+ <dt id="user~2"><a class="permalink" href="#user~2"><code class="Dv">user</code></a></dt>
+ <dd>Committer's username. This is the only field guaranteed to
+ be set.</dd>
+ </dl>
+ </dd>
+ <dt id="author"><a class="permalink" href="#author"><code class="Dv">author</code></a></dt>
+ <dd>An object with the author information. Has the same fields as
+ the <code class="Dv">committer</code> but may be unset.</dd>
+ <dt id="date"><a class="permalink" href="#date"><code class="Dv">date</code></a></dt>
+ <dd>Number, representing the number of seconds since the Epoch in
+ UTC.</dd>
+ <dt id="short_message"><a class="permalink" href="#short_message"><code class="Dv">short_message</code></a></dt>
+ <dd>The first line of the commit message. This field is always
+ set.</dd>
+ <dt id="message"><a class="permalink" href="#message"><code class="Dv">message</code></a></dt>
+ <dd>The complete commit message, may be unset.</dd>
+ <dt id="diffstat"><a class="permalink" href="#diffstat"><code class="Dv">diffstat</code></a></dt>
+ <dd>An object with the summarized changes, may be unset. Contains
+ a <code class="Dv">files</code> field with an array of objects
+ describing the changes per-file and a
+ <code class="Dv">total</code> field with the cumulative
+ changes. The changes per-file contains the following fields:
+ <p class="Pp"></p>
+ <dl class="Bl-tag Bl-compact">
+ <dt id="action"><a class="permalink" href="#action"><code class="Dv">action</code></a></dt>
+ <dd>A string describing the action, can be
+ “added”, “deleted”,
+ “modified”, “mode changed”, or
+ “unknown”.</dd>
+ <dt id="file"><a class="permalink" href="#file"><code class="Dv">file</code></a></dt>
+ <dd>The file path.</dd>
+ <dt id="added"><a class="permalink" href="#added"><code class="Dv">added</code></a></dt>
+ <dd>The number of lines added.</dd>
+ <dt id="removed"><a class="permalink" href="#removed"><code class="Dv">removed</code></a></dt>
+ <dd>The number of lines removed.</dd>
+ </dl>
+ <p class="Pp">The <code class="Dv">total</code> object contains
+ two fields: <code class="Dv">added</code> and
+ <code class="Dv">removed</code> which are the number of
+ added and removed lines respectively.</p>
+ </dd>
+ </dl>
+ </dd>
+ <dt id="branch-deleted"><a class="permalink" href="#branch-deleted"><code class="Dv">branch-deleted</code></a></dt>
+ <dd>The branch deleted notifications has the following fields, all
+ guaranteed to be set:
+ <dl class="Bl-tag Bl-compact">
+ <dt id="repo~2"><a class="permalink" href="#repo~2"><code class="Dv">repo</code></a></dt>
+ <dd>The repository name as string.</dd>
+ <dt id="ref"><a class="permalink" href="#ref"><code class="Dv">ref</code></a></dt>
+ <dd>The removed branch reference.</dd>
+ <dt id="id~2"><a class="permalink" href="#id~2"><code class="Dv">id</code></a></dt>
+ <dd>The hash of the commit pointed by the deleted branch.</dd>
+ </dl>
+ </dd>
+ <dt id="tag~2"><a class="permalink" href="#tag~2"><code class="Dv">tag</code></a></dt>
+ <dd>The tag notification has the following fields, all guaranteed to
+ be set:
+ <dl class="Bl-tag">
+ <dt>repo</dt>
+ <dd>The repository name as string.</dd>
+ <dt>tag</dt>
+ <dd>The tag reference.</dd>
+ <dt>tagger</dt>
+ <dd>The user information, with the same format of the
+ <code class="Dv">committer</code> field for the
+ <code class="Dv">commit</code> notification but with all the
+ field guaranteed to be set.</dd>
+ <dt id="date~2"><a class="permalink" href="#date~2"><code class="Dv">date</code></a></dt>
+ <dd>Number, representing the number of seconds since the Epoch in
+ UTC.</dd>
+ <dt id="object"><a class="permalink" href="#object"><code class="Dv">object</code></a></dt>
+ <dd>The object being tagged. It contains the fields
+ <code class="Dv">type</code> with the object type and
+ <code class="Dv">id</code> with the object id being
+ tagged.</dd>
+ <dt id="message~2"><a class="permalink" href="#message~2"><code class="Dv">message</code></a></dt>
+ <dd>The tag message.</dd>
+ </dl>
+ </dd>
+ </dl>
+ </dd>
+ </dl>
</dd>
</dl>
</section>
branch "main"
tag namespace "refs/tags/"
}
+
+ notify {
+ branch "main"
+ reference namespace "refs/tags/"
+ email to openbsd-ports-changes@example.com
+ }
}
# Use a larger request timeout value:
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - f1e41cdc74344c846a6d0a6b02b9d9532b31c2a9
blob + 2f8b5bbb49b15a58dc48a06aeea02fd1de696423
--- gotsh.1.html
+++ gotsh.1.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - b0faf87c34851d6335d9fc6110602f19f1728f46
blob + 1b034f69fee6aabb1422cfab705d85302fdfd278
--- gotwebd.8.html
+++ gotwebd.8.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 07e53fc18864a040aa443da5482b6d54c776b47a
blob + bf258f30500ae7840e0c6f063860270ffda2ef16
--- gotwebd.conf.5.html
+++ gotwebd.conf.5.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
blob - 7dff074ebdfcd979b5a081a73942024e37f8adab
blob + 91892d4bca9fd1e8c531c15615c5dddbea0b5a34
--- tog.1.html
+++ tog.1.html
</section>
</main>
<div class="foot" role="doc-pagefooter" aria-label="Manual footer
- line"><span class="foot-left"></span><span class="foot-date">March 11,
+ line"><span class="foot-left"></span><span class="foot-date">April 23,
2024</span> <span class="foot-os">OpenBSD 7.5</span></div>
</body>
</html>
