| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It can't be used correctly and has been removed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes several RFC 4287 violations:
> 4.1.1. The "atom:feed" Element
> o atom:feed elements MUST contain exactly one atom:id element.
> o atom:feed elements SHOULD contain one atom:link element with a rel
> attribute value of "self". This is the preferred URI for
> retrieving Atom Feed Documents representing this Atom feed.
> o atom:feed elements MUST contain exactly one atom:updated element.
An atom:id element is generated from cgit_currentfullurl(), and an
atom:link element with a rel attribute of "self" is generated with
the same URL. An atom:updated element is generated from the date
of the first commit in the revision walk.
> 4.1.2. The "atom:entry" Element
> o atom:entry elements MUST NOT contain more than one atom:content
> element.
The second atom:content element with the type of "xhtml" is removed.
> 4.2.6. The "atom:id" Element
> Its content MUST be an IRI, as defined by [RFC3987]. Note that the
> definition of "IRI" excludes relative references. Though the IRI
> might use a dereferencable scheme, Atom Processors MUST NOT assume it
> can be dereferenced.
The atom:id elements for commits now use URNs in the "sha1" or
"sha256" namespaces. Although these are not registered URN namespaces,
they see use in the wild, for instance as part of magnet URIs.
|
|
|
|
| |
This version of cgit is modified and doesn't track upstream releases.
|
| |
|
|
|
|
| |
OpenBSD tar(1) has no -J.
|
|
|
|
| |
RIP.
|
| |
|
| |
|
|
|
|
|
| |
For example any URL that starts with a real repo name but isn't
valid.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
So that only "published" text files are included.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Previously it was only used if owners were displayed on the index.
|
|
|
|
|
| |
It's not documented that you can set logo to empty string to remove
it, I just noticed by reading print_header.
|
| |
|
| |
|
|
|
|
|
| |
Lua support is unused and the dlsym fwrite/write hacks horrify me.
Clean it up.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This correctly preserves whitespace in browsers without CSS, as an
alternative to [1].
[1]: https://80x24.org/cgit.git/commit/?id=7c692e6137697de8a8473c4de5c3de4fb03a2989
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our generation of HTML triggers many small write(2) syscalls
which is inefficient.
Time output on a horrible query against my git.git mirror
shows significant performance improvement:
QUERY_STRING='id=2b93bfac0f5bcabbf60f174f4e7bfa9e318e64d5&id2=d6da71a9d16b8cf27f9d8f90692d3625c849cbc8'
PATH_INFO=/mirrors/git.git/diff
export QUERY_STRING PATH_INFO
time ./cgit >/dev/null
Before:
real 0m1.585s
user 0m0.904s
sys 0m0.658s
After:
real 0m0.750s
user 0m0.666s
sys 0m0.076s
|
|
|
|
|
|
|
| |
The title attribute was being set to the same value as the anchor
element text.
Signed-off-by: Chris Mayo <aklhfex@gmail.com>
|
|
|
|
|
|
|
| |
For browsers on low-end machines running browsers without CSS
support, the default tree view displayed "logplain" when it
should be "log plain". Stop relying on CSS and add a space
in between elements to improve accessibility.
|
|
|
|
|
|
| |
Text-based browsers without CSS support show all the decorations
bunched together without spacing. Rely on a whitespace instead
of CSS support.
|
|
|
|
|
| |
This preserves formatting readable for users of text-based browsers
without CSS support.
|
|
|
|
|
|
|
|
|
|
|
| |
Text-based browsers (and some GUI browsers such as dillo) display
the pageheader as:
"summaryrefslogtreecommitdiff"
This is difficult-to-read. Improve accessibility for users who
cannot run memory-hungry browsers by using whitespace instead of
relying on CSS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently a commit note is shown as:
Notes
Notes:
<note text>
Change to:
Notes
<note text>
Signed-off-by: Chris Mayo <aklhfex at gmail.com>
|
|
|
|
|
| |
ctags does not create the tags file if the input file contains nothing
worth tagging, and htagml errors if there is no tags file to load.
|
|
|
|
| |
Otherwise ctags can't figure out if the input is a lex or yacc file.
|
| |
|
| |
|