| Age | Commit message (Collapse) | Author | Lines |
|
A tree can hold two entries of one name when fsck is off, and the walk
went on after the first answered. A second file put two responses in one
body, and a directory under the same name printed headers from the
mimetype string the first had already freed.
|
|
Git 2.55 moved object sizes from unsigned long to size_t. The two are
the same type on 64-bit hosts, but not on a 32-bit one, where GCC 14
rejects the mismatched pointers, so cgit stopped compiling there.
|
|
Five copies of the test and four of the error page had to agree by
hand. The new check pins the four refusals, which no test covered.
|
|
Git's DEVELOPER=1 build turns on -Wwrite-strings as an error, and the
literals stored through plain char pointers failed cgit's own objects
there. The exec filter's argv takes the cast execvp needs once, the
way git's run-command does.
|
|
Archives, packs and the HEAD file went out as octet-stream or gzip with
a UTF-8 charset on the end, since only the plain and about pages cleared
it.
|
|
The four pages that refuse a blob over max-blob-size each said it in
their own way, two of them in lower case, and the blame page ended its
binary notice with a full stop no other error carries.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AUTHORS now records the upstream developers as the project's history
rather than as maintainers of the fork.
|
|
Only the tree view honoured the limit, and only after loading the whole
object. The default moves from unlimited to 10 MB so a fresh install
never buffers a huge object whole. Zero still turns the limit off.
|
|
A blob requested by ref with an unknown path fell through to the commit
object and was served with a 200 instead of a 404. Two error pages
passed a null pointer to a %s format when the request carried no object
id, and the error pages left the layout open.
|
|
Everything the build generates now lands in build/, so a clean is a
single remove and the source tree stays free of build output.
|