Commit message (Collapse) | Author | Files | Lines | ||
---|---|---|---|---|---|
2025-05-23 | meta.capim: Add :dependencies key | EuAndreh | 1 | -0/+7 | |
2025-05-15 | Revamp setup of i18n, now with gotext(0) | EuAndreh | 19 | -192/+734 | |
2025-05-11 | Finish branches.html and setup i18n of manpages and HTML strings | EuAndreh | 15 | -30/+1481 | |
2025-05-06 | src/gistatic.go: Add missing trailing newline to usage() output | EuAndreh | 1 | -1/+1 | |
2025-05-05 | src/gistatic.go: Use ExitIf() from gobang | EuAndreh | 1 | -3/+1 | |
2025-05-05 | src/gistatic.go: Tweak indentation 💅 | EuAndreh | 1 | -5/+3 | |
2025-05-04 | git mv meta.json meta.capim | EuAndreh | 2 | -3/+3 | |
2025-05-04 | Make: Use $< over $? | EuAndreh | 1 | -1/+1 | |
2025-05-02 | Switch from POSIX sh to Go | EuAndreh | 59 | -3030/+294 | |
2025-05-02 | WIP: Commit sh code as-is | EuAndreh | 3 | -1261/+620 | |
2025-05-02 | Makefile: Clean-up old stuff | EuAndreh | 1 | -100/+59 | |
2025-05-02 | Add mkdeps.sh and deps.mk | EuAndreh | 2 | -0/+10 | |
2025-05-02 | mv src/gitstatic{,.in} | EuAndreh | 1 | -0/+0 | |
2025-05-02 | git mv description meta.json | EuAndreh | 2 | -1/+3 | |
2025-05-02 | rm CHANGELOG.md f | EuAndreh | 2 | -104/+0 | |
2025-05-02 | rm -rf doc/ | EuAndreh | 5 | -54/+0 | |
2025-05-02 | rm -rf tests/resources/repositories/repo-{1,2}/.gitdir/info/ | EuAndreh | 2 | -12/+0 | |
2025-05-02 | rm tests/resources/repositories/repo-{1,2}/.gitdir/hooks/*.sample | EuAndreh | 26 | -1580/+0 | |
2025-03-20 | rm COPYING | EuAndreh | 1 | -661/+0 | |
2025-01-06 | m | EuAndreh | 3 | -13/+369 | |
2025-01-06 | m | EuAndreh | 7 | -1120/+344 | |
2023-04-14 | Cleanup repo, reinit in sh | EuAndreh | 34 | -4418/+1350 | |
2023-04-14 | rm -rf aux/ | EuAndreh | 27 | -1473/+0 | |
2021-09-10 | TODOs.md: Add #task-1554614f-2e33-616d-d021-70828dbf0381 | EuAndreh | 1 | -0/+8 | |
2021-09-08 | src/gistatic.in: Fix HTML indentation (probably a typo while editing) | EuAndreh | 1 | -1/+6 | |
2021-09-08 | src/gistatic.in: Finish refs page with signatures, start commit pages | EuAndreh | 1 | -20/+54 | |
- actually implement HTML escaping; - include cached_run for (hopefully) reusing across HTML generating functions; - include the repository name on the $CACHE_DIR; - use the existence of a .asc file to decide on which HTML to output on the refs page; - implement all FIXMEs but the WIP one on the commit HTML generation. | |||||
2021-09-08 | src/gistatic.in: Initial sh version | EuAndreh | 3 | -2/+756 | |
I got a bit frustrated that libgit2 didn't offer an API or "git archive" commands. I started implementing generating tarballs from scratch in src/tar.c and I'm quite liking it: the specification is very small, and the code can be very simple, since all I'm doing is writing fresh tarballs, and not reading or updating them. However I felt a bit locked-in to libgit2 itself, and what a detour from my original goal that is, and the question "what should libgit2 provide" came up to my mind. This made me realize that libgit2 is playing catch-up with Git itself, for as long as Git doesn't explicit has an explicit API, a standard, a public version of its internal libgit.a, or something like that. In fact, I'm locked in to Git, even. So even though a C version would probably be much faster, it wouldn't really have less dependencies, and that's what I'm actually optimising for: having the software be as portable as possible. On that front, C is unbeatable with sh as a close second. But the extreme portability of C aren't being fully exploited here: libgit2 does depend on non-POSIX things like CMake (and quick grep even shows references to -D_GNU_SOURCE!!), and Git's Makefile itself isn't POSIX at all. The point is: by depending on either Git or libgit2, I'm already loosing many selling points of writing the software in C, and sh becomes much more attractive. Had existed a common DVCS interface that could make me decouple gistatic from Git somehow I would insist a bit more in C, but now I'm switching to sh. The fact that I was able to get further with sh in one sitting than I did with C shows that a) I'm a bit less fluent in C than I would like (at least for now ^^) and b) that it is actually much simpler to do. I am quite satisfied with the quality of C code that I got so far. The error handling and propagation is pretty robust, and the implementation is very disciplined. I did most of the development with Valgrind, and other sanitizers would help even further, with some fuzzers on top. | |||||
2021-09-08 | TODOs.md: Add #question-ab994373-9c09-c4f9-07cf-962f64443231 | EuAndreh | 1 | -0/+3 | |