$ git clone --bare
+$ got clone
   https://github.com/openbsd/src.git
 Alternatively, for quick and dirty local testing of
     got a new Git repository could be created and
@@ -3134,13 +3165,6 @@
 

 $ 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:
-
-$ cd /var/git/src.git
-$ git fetch origin
-  master:refs/remotes/origin/master
 Rebase the local “master” branch to merge the new
     changes that are now visible on the “origin/master”
   branch:
@@ -3472,9 +3496,6 @@ remote "origin" {
     git(1) to perform some tasks.
     In particular:
 
-  Reading from remote repositories over HTTP or HTTPS protocols requires
-      git-clone(1) and
-      git-fetch(1).
   Writing to remote repositories over HTTP or HTTPS protocols requires
       git-push(1).
   The creation of merge commits with more than two parent commits requires
@@ -3487,7 +3508,7 @@ remote "origin" {
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - abf21812acf06903ae98b7f6185dfbb5fd5faea0
blob + 1917a233a6eb9eee6d95a52e39bfc9f9c1e693e3
--- got.conf.5.html
+++ got.conf.5.html
@@ -306,7 +306,7 @@
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - 64a934e2426369f0c2dc3b0cbfee24f5e2971252
blob + 3908702f5fa21b3db0aaa5e2411ce87751245062
--- gotadmin.1.html
+++ gotadmin.1.html
@@ -424,7 +424,7 @@
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - 8a107c269f9a4f65962e971554b2f6a60c16a1c5
blob + dd544668c4959201fb0376ff2340a043b005e0d9
--- gotctl.8.html
+++ gotctl.8.html
@@ -86,7 +86,7 @@
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - 15a37fbb779dce66cf83bc7ee8e8d84da6ca74a5
blob + 934c1d4fe17f4b57a6e53a0d6b195b06cb45a367
--- gotd.8.html
+++ gotd.8.html
@@ -99,7 +99,7 @@
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - 30a53bb588f951cd2c2246bc9e49a9861e713af3
blob + 10d040b23b01c6dd5e2dbd9b635a4689c9b3f97a
--- gotd.conf.5.html
+++ gotd.conf.5.html
@@ -202,6 +202,206 @@
         gotd.conf. These namespaces are always protected
         and even attempts to create new references in these namespaces will
         always be denied.
+  
+  notify
+    {...}
+  The notify directive enables notifications about
+      new commits or tags added to the repository.
+    Notifications via email require an SMTP daemon which accepts
+        mail for forwarding without requiring client authentication or
+        encryption. On OpenBSD the
+        smtpd(8) daemon can be
+        used for this purpose. The default content of email notifications looks
+        similar to the output of the got log -d
+      command.
+    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 gotd(8) by
+        triggering arbitrary post-commit actions via the HTTP server.
+    The notify directive expects
+        parameters which must be enclosed in curly braces. The available
+        parameters are as follows:
+    
+      branch
+        name
+      Send notifications about commits to the named branch. The
+          name 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 branch nor a
+          reference namespace are specified then changes
+          to any reference will trigger notifications.
+      reference
+        namespace namespace
+      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
+          branch nor a reference
+          namespace are specified then changes to any reference will
+          trigger notifications.
+      email
+        [from sender]
+        to recipient
+        [reply to responder]
+        [relay hostname
+        [port port]]
+      Send notifications via email to the specified
+          recipient. This directive may be specified
+          multiple times to build a list of recipients to send notifications to.
+        The recipient must be an email
+            addresses that accepts mail. The sender will
+            be used as the From address. If not specified, the sender defaults
+            to an email address composed of the user account running
+            gotd(8) and the local
+            hostname.
+        If a responder is specified via the
+            reply to directive, the
+            responder 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 sender,
+            for example.
+        By default, mail will be sent to the SMTP server listening
+            on the loopback address 127.0.0.1 on port 25. The
+            relay and port
+            directives can be used to specify a different SMTP server address
+            and port.
+      
+      url
+        URL [user
+        user password
+        password [insecure]]
+      Send notifications via HTTP. This directive may be specified multiple
+          times to build a list of HTTP servers to send notifications to.
+        The notification will be sent as a POST request to the
+            given URL, 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.
+        The optional user and
+            password directives enable HTTP Basic
+            authentication. If used, both a user and a
+            password must be specified. The
+            password must not be an empty string. Unless
+            the insecure option is specified the
+            notification target URL must be a
+            “https://” URL to avoid leaking of authentication
+            credentials.
+        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:
+        
+          commit
+          The commit notification object has the following fields. Except
+              where noted, all are optional.
+            
+              short
+              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.
+              repo
+              The repository name as string.
+              id
+              The commit ID as string, may be abbreviated.
+              committer
+              An object with the committer information with the following
+                  fields:
+                
+                
+                  full
+                  Committer's full name.
+                  name
+                  Committer's name.
+                  mail
+                  Committer's mail address.
+                  user
+                  Committer's username. This is the only field guaranteed to
+                      be set.
+                
+              
+              author
+              An object with the author information. Has the same fields as
+                  the committer but may be unset.
+              date
+              Number, representing the number of seconds since the Epoch in
+                  UTC.
+              short_message
+              The first line of the commit message. This field is always
+                  set.
+              message
+              The complete commit message, may be unset.
+              diffstat
+              An object with the summarized changes, may be unset. Contains
+                  a files field with an array of objects
+                  describing the changes per-file and a
+                  total field with the cumulative
+                  changes. The changes per-file contains the following fields:
+                
+                
+                  action
+                  A string describing the action, can be
+                      “added”, “deleted”,
+                      “modified”, “mode changed”, or
+                      “unknown”.
+                  file
+                  The file path.
+                  added
+                  The number of lines added.
+                  removed
+                  The number of lines removed.
+                
+                The total object contains
+                    two fields: added and
+                    removed which are the number of
+                    added and removed lines respectively.
+              
+            
+          
+          branch-deleted
+          The branch deleted notifications has the following fields, all
+              guaranteed to be set:
+            
+              repo
+              The repository name as string.
+              ref
+              The removed branch reference.
+              id
+              The hash of the commit pointed by the deleted branch.
+            
+          
+          tag
+          The tag notification has the following fields, all guaranteed to
+              be set:
+            
+              repo
+              The repository name as string.
+              tag
+              The tag reference.
+              tagger
+              The user information, with the same format of the
+                  committer field for the
+                  commit notification but with all the
+                  field guaranteed to be set.
+              date
+              Number, representing the number of seconds since the Epoch in
+                  UTC.
+              object
+              The object being tagged. It contains the fields
+                  type with the object type and
+                  id with the object id being
+                tagged.
+              message
+              The tag message.
+            
+          
+        
+      
+    
   
 
 
@@ -244,6 +444,12 @@ repository "openbsd/ports" {
 		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:
@@ -265,7 +471,7 @@ connection {
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - f1e41cdc74344c846a6d0a6b02b9d9532b31c2a9
blob + 2f8b5bbb49b15a58dc48a06aeea02fd1de696423
--- gotsh.1.html
+++ gotsh.1.html
@@ -157,7 +157,7 @@
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - b0faf87c34851d6335d9fc6110602f19f1728f46
blob + 1b034f69fee6aabb1422cfab705d85302fdfd278
--- gotwebd.8.html
+++ gotwebd.8.html
@@ -188,7 +188,7 @@ server "example.com" {
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - 07e53fc18864a040aa443da5482b6d54c776b47a
blob + bf258f30500ae7840e0c6f063860270ffda2ef16
--- gotwebd.conf.5.html
+++ gotwebd.conf.5.html
@@ -236,7 +236,7 @@ owner = "Your Name"
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5
 
 
blob - 7dff074ebdfcd979b5a081a73942024e37f8adab
blob + 91892d4bca9fd1e8c531c15615c5dddbea0b5a34
--- tog.1.html
+++ tog.1.html
@@ -847,7 +847,7 @@
 
 
 March 11,
+  line">April 23,
   2024 OpenBSD 7.5