| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
|
|
|
|
| |
Also bump the message cap to 1024 because that is ostensibly useful
for replying to older messages.
|
| |
|
|
|
|
|
| |
There are probably better things to sort by but title definitely
always exists.
|
|
|
|
|
| |
This makes it even faster. From ~1s on a sqlite3.c amalgamation to
~0.85s.
|
|
|
|
|
|
|
|
|
|
| |
Since ctags only ever produces regular expressions of the form
/^re$/ or /^re/ with no other special characters, instead unescape
the pattern and simply use strncmp.
Running on a sqlite3.c amalgamation, the regex version takes ~37s
while the strncmp version takes ~1s, producing identical output.
Big win!
|
| |
|
| |
|
| |
|
|
|
|
| |
This fixes badly indented comments.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Only add comments for blame groups larger than 1 line by default.
|
| |
|
|
|
|
| |
I want to implement this but it requires more complex lexing.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It's like proto-xenogenesis-series.
|
| |
|
| |
|
|
|
|
|
| |
Some shells write to standard error from type when the command is
not found. command -v is silent.
|
| |
|
| |
|
|
|
|
|
| |
Idea is that LESS=FRX makes it the same for short files... But less
on OpenBSD behaves weirdly. I'll see.
|
| |
|
|
|
|
| |
Felt so short compared to the previous full-length novel.
|
|
|
|
|
|
|
| |
Some good stories but 99% downers. Feels like the editors fell for
thinking that "feminist speculative fiction" can only be about
suffering. Where are the stories of pride and empowerment? Balance
it out, please.
|
| |
|
| |
|
|
|
|
|
| |
Non-daylight aware colour temperature adjustment just doesn't work
right.
|
|
|
|
| |
lol
|
|
|
|
|
| |
Contemptible protagonist, long and tedious. Would not have ever
read Year of the Flood if I had read this one first.
|
|
|
|
| |
And clean up some other things.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
efc7765b Release 0.5.11.4.
a5316982 eval: Do not cache value of eflag in evaltree
9e0f6a77 Release 0.5.11.3.
5f770b12 jobs: Only block in waitcmd on first run
git-subtree-dir: bin/dash
git-subtree-split: efc7765b5d7a4dcd23dbf8fbde35a843f5f222ca
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
It can't be used correctly and has been removed.
|
| | |
|
| |
| |
| |
| | |
... seriously this software.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
|\ \ |
|