exman, branch 2066.8manuals for other systems
https://git.causal.agency/exman/atom?h=2066.82024-11-06T01:35:38+00:00Update to OpenBSD 7.62024-11-06T01:35:38+00:00Štěpán Němecstepnem@smrk.net2024-10-08T17:36:57+00:00urn:sha1:4d6719d5579a69fb0e38b3ba0e402b86fbb515faUpdate to Linux man-pages 6.9.12024-11-06T01:35:38+00:00Štěpán Němecstepnem@smrk.net2024-06-20T06:35:38+00:00urn:sha1:1837e67c07a1b38c3129fce2eb8c437118a017e9Update to Linux man-pages 6.92024-11-06T01:35:38+00:00Štěpán Němecstepnem@smrk.net2024-06-17T07:47:31+00:00urn:sha1:e11cc40b9517fa9865b3cbe07ff4f540fd41456c
In 6.8, Linux man-pages "build system" changed so that running
GNU make (together with a number of other tools) is required to
arrive at the final form of the man pages.[1] That said, the only
currently observable difference seems to be "Linux man-pages (unreleased)"
instead of, say, "Linux man-pages 6.9" in the man page footer
(and the release announcement seems to support that observation),
so this commit preserves the install-by-copying procedure, only
adapting the path extraction. The installed version is always
recorded in exman.1, anyway.
[1]
6.8 release announcement:
https://lore.kernel.org/linux-man/je5cqtxomjonmjyzdkhalfxr5idkselxxgfybjtwupnocqgaai@hue4yy7hvory/
For more context, see e.g. (Gentoo and Debian reactions):
https://lore.kernel.org/linux-man/87ttjm8ero.fsf@gentoo.org/
https://lore.kernel.org/linux-man/kt2jczwpcjm7ylszg37vbg5ubjudgxw3fjhuiwbgfrq2f3x73b@rdkpvaie73kg/
Update to NetBSD 10.02024-05-15T23:15:04+00:00Štěpán Němecstepnem@smrk.net2024-04-11T06:48:26+00:00urn:sha1:65af1c7fd63d5e0f8148a81b38eefa8b811b1742Update to OpenBSD 7.52024-05-15T23:15:04+00:00Štěpán Němecstepnem@smrk.net2024-04-09T09:30:14+00:00urn:sha1:5b7b3ab47064a70fc1d12bd1595a25ba22f65801Update to Linux man-pages 6.72024-03-22T01:18:06+00:00Štěpán Němecstepnem@smrk.net2024-03-21T08:55:26+00:00urn:sha1:92f0cfcab25d4b43c36b48aa507e4b1183da14d1Update to Linux man-pages 6.062024-03-03T23:14:23+00:00Štěpán Němecstepnem@smrk.net2024-02-14T17:56:21+00:00urn:sha1:44161de68f4a787ff0ec725f5452da9c48b5dd85Update to FreeBSD 14.02023-11-27T21:12:02+00:00Štěpán Němecstepnem@smrk.net2023-11-22T12:54:42+00:00urn:sha1:ef24a24183911e370ec9773d4e9fa47e13a91ab5Update to OpenBSD 7.42023-10-16T19:38:35+00:00Kusonekokusoneko@kusoneko.moe2023-10-16T16:40:07+00:00urn:sha1:2b021725b64a1ca1d026518ebfca077abf33e72d
Signed-off-by: Kusoneko <kusoneko@kusoneko.moe>
Update to Linux man-pages 6.052023-10-11T23:53:29+00:00Štěpán Němecstepnem@smrk.net2023-08-03T10:48:46+00:00urn:sha1:5105b148b49a80da366fbd9f43d044903889ca18
le='2018-02-04 11:42:54 -0500'>2018-02-04
This will allow us to reuse the same logic to add clone URL <link/>
elements to the header of all repo-specific pages in order to support
the rel-vcs microformat.
Signed-off-by: John Keeping <john@keeping.me.uk>
When removing the ".git" suffix of a non-bare repository, also remove
the trailing slash for compatibility with cgit_repobasename().
Signed-off-by: Lukas Fleischer <cgit@cryptocrack.de>
Serving cgit via https and getting avatar via http gives error messages
about untrusted content. This decides whether or not to use https link
by looking at the environment variable HTTPS, which is set in CGI.
This prints the diffstat but stops before printing (or generating) any
of the body of the diff.
No cgitrc option is added here so that we can wait to see how useful
this is before letting people set it as the default.
Suggested-by: Konstantin Ryabitsev <mricon@kernel.org>
Signed-off-by: John Keeping <john@keeping.me.uk>
This will allow us to introduce a new "stat only" diff mode without
needing an explosion of mutually incompatible flags.
The old "ss" query parameter is still accepted in order to avoid
breaking saved links, but we no longer generate any URIs using it;
instead the new "dt" (diff type) parameter is used.
Signed-off-by: John Keeping <john@keeping.me.uk>
Specifying a nonexistent README file via the readme option is sometimes
useful, e.g. when using scan-path and setting a global default.
Currently, we check whether there is only one option in the readme
option and, if so, we choose that file without checking whether it
exists. As a consequence, all repositories are equipped with an about
link in the aforementioned scenario, even if there is no about file.
Remove the early check for the number of keys and always check whether
the file exists instead.
Signed-off-by: Lukas Fleischer <cgit@cryptocrack.de>
This is slightly more involved than just bumping the version number
because it pulls in a change to convert the commit buffer to a slab,
removing the "buffer" field from "struct commit". All sites that access
"commit->buffer" have been changed to use the new functions provided for
this purpose.
Signed-off-by: John Keeping <john@keeping.me.uk>
It looks like cached patches are truncated to the nearest 1024-byte
boundary in the patch body. E.g.:
> mricon@nikko:[/tmp]$ wget -O no-cache
> "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=6e1b4fdad5157bb9e88777d525704aba24389bee"
...
> 2014-06-11 15:34:51 (80.4 MB/s) - ‘no-cache’ saved [4767]
Patch is complete, without truncation. Next hit, with cache in place:
> mricon@nikko:[/tmp]$ wget -O yes-cache
> "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=6e1b4
> fdad5157bb9e88777d525704aba24389bee"
...
> 2014-06-11 15:35:01 (17.0 MB/s) - ‘yes-cache’ saved [4096/4096]
Length truncated to 4096. The cache on disk looks truncated as well, so
the bug must me during the process of saving cache. The same is true for
larger patches:
> mricon@nikko:[/tmp]$ wget -O no-cache
> "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=2840c566e95599cd60c7143762ca8b49d9395050"
...
> 2014-06-11 15:41:33 (1.07 MB/s) - ‘no-cache’ saved [979644]
979644 bytes with a cache-miss
> mricon@nikko:[/tmp]$ wget -O yes-cache
> "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=2840c
> 566e95599cd60c7143762ca8b49d9395050"
...
> 2014-06-11 15:41:46 (1.05 MB/s) - ‘yes-cache’ saved [978944]
978944 (956KB exactly) with a cache-hit
Since the "html" functions use raw write(2) to STDIO_FILENO, we don't
notice problems with most pages, but raw patches write using printf(3).
This is fine if we're outputting straight to stdout since the buffers
are flushed on exit, but we close the cache output before this, so the
cached output ends up being truncated.
Make sure the buffers are flushed when we finish outputting a patch so
that we avoid this.
No other UIs use printf(3) so we do not need to worry about them.
Actually, it's slightly more interesting than this... since we don't set
GIT_FLUSH, Git decides whether or not it will flush stdout after writing
each commit based on whether or not stdout points to a regular file (in
maybe_flush_or_die()).
Which means that when writing directly to the webserver, Git flushes
stdout for us, but when we redirect stdout to the cache it points to a
regular file so Git no longer flushes the output for us.
The patch is still correct, but perhaps the full explanation is
interesting!
Reported-by: Konstantin Ryabitsev <mricon@kernel.org>
If you search for a bogus range string here:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/
Using something like "range" and "qwerty123456", it returns an "Internal
Server Error" and the following in the logs:
> [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] fatal:
> ambiguous argument 'qwerty123456': unknown revision or path not in the
> working tree., referer:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
> [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] Use '--' to
> separate paths from revisions, like this:, referer:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
> [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] 'git <command>
> [<revision>...] -- [<file>...]', referer:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
> [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] Premature end
> of script headers: cgit, referer:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
The cache will kick in, so if you search for the same string again,
it'll show an empty range, so you have to change the bogus strings each
time.
This is because we just pass the arguments straight to Git's revision
parsing machinery which die()s if it cannot parse an argument, printing
the above to stderr and exiting.
The patch below makes it a bit friendlier by just ignoring unhandled
arguments, but I can't see an easy way to report errors when we can't
parse revision arguments without losing the flexibility of supporting
all of the revision specifiers supported by Git.
Reported-by: Konstantin Ryabitsev <mricon@kernel.org>
prefixcmp() and suffixcmp() have been remove, functionality is now
provided by starts_with() and ends_with(). Retrurn values have been
changed, so instead of just renaming we have to fix logic.
Everything else looks just fine.
For example, if I have two repos (remove-suffix is enabled):
/foo
/foo/bar
http://cgit/foo/bar/ is interpreted as "repository 'foo', command 'bar'"
instead of "repository 'foo/bar'"